#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: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Ok, I did some investigation, and now STATIC_URL and quitting the tests
when the server hits forever-loop should work.
Attached is an incremental patch for the .10. patch. The stuff in my patch
isn't polished at all, but it should show the problematic places, and at
least some way to fix them.
One thing about documentation: I wonder if it is a good advice to do
selenium setup / quit in tearDown and setUp. This makes each test_method
take about 7 seconds on my system (for each test method, start and stop
Firefox). Would it be better to advice the use of tearDownClass and
setUpClass? This way Firefox is started only once per test class. On the
other hand, this has a bit bigger chance of hitting cross-test
dependencies. Maybe at least mention in the documentation that this is
also possible? From my point of view, this documentation polishing can be
done after initial commit.
--
Ticket URL: <https://code.djangoproject.com/ticket/2879#comment:94>
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.
