#2879: Add live test server support to test framework
-------------------------------------+-------------------------------------
Reporter: Mikeal Rogers | Owner: devin
<mikeal@…> | Status: new
Type: New feature | Version:
Component: Testing framework | Resolution:
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* cc: anssi.kaariainen@… (added)
Comment:
Spotted one comment which is a bit misleading.
The comment containing the snippet "the threads do not share the same
connection's cursor (unless if using in-memory sqlite)." isn't exactly
correct: This is not about sharing cursors, but that in general the setup
must be:
- `TestCase`: sets up database state, commits. Makes request (by selenium
or whatever have you).
- `TestServer`: serves the request normally, this means usually a
transaction is made and committed.
- `TestCase`: checks database state (yet another transaction).
So, that comment might need updating. Also, it would be good to document
the above. Maybe all that is needed is: "remember to commit changes to db-
state before making requests". If there is no commit, the test-server
thread's connection will not see those changes, unless using inmemory-
sqlite.
--
Ticket URL: <https://code.djangoproject.com/ticket/2879#comment:86>
Django <https://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-updates@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.
