#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 tomchristie):

 Attached patch does the following:

 1. Rename `SeleniumTestCase` to `SeleniumRCTestCase`, settings to
 `SELENIUM_RC_HOST`, `SELENIUM_RC_PORT`, `SELENIUM_RC_BROWSER`, and updates
 docs accordingly.
 2. Move `SeleniumTestCase` into `django.contrib.selenium`.
 3. Check for Selenium connection during the first test run, rather than at
 time of import.
 4. Move "Wait for the Django server to be ready" code out of
 `SeleniumTestCase`, into `LiveServerTestCase`.

 Feel free to pull out whatever you think is useful and chuck out the rest.

 I've take a look at using !WebDriver instead - it seems pretty complete to
 me, it's much nicer not having to have the Selenium Server running, and it
 looks a lot faster to setup/teardown. (A sample test doing a single URL
 load tended to complete in 2.0-2.5 seconds, compared to 5.0-6.0 seconds
 for the RC version).  The API is perhaps a little more verbose than it
 could be, but there's nothing obviously preventing the existing admin
 tests from being re-written for !WebDriver.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/2879#comment:69>
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.

Reply via email to