#11101: Oracle fails admin_view tests when the whole suite is run -- transaction
problem?
---------------------------------------------------+------------------------
Reporter: mboersma | Owner: mboersma
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: oracle
transaction test
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by ramiro):
Our move from doctests to unit tests for the Django test has exacerbated
this problem and it can be seen even in the most basic tests that use
fixtures, e.g.
`modeltests.fixtures.FixtureLoadingTests.{test_compress_format_loading,test_compressed_loading}`
in that order. The second test method doesn't get a clean DB state, when
it starts the DB contains an `Article` record loaded from the
`initial_data` fixture (expected) AND the record loaded by the `loaddata`
management call in the previous test method (unexpected).
Failure rate of our suite under Oracle is currently very high because this
basic unit test assumption is broken.
AFAICS, this issue can affect any app test case that uses fixtures, not
only the Django test suite.
--
Ticket URL: <http://code.djangoproject.com/ticket/11101#comment:7>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
