pip install django-nose-qunit.
Add 'django_nose_qunit' to your INSTALLED_APPS setting.
Ensure that you’re using nose as your test runner by using the following Django setting
TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'
Enable the nose plugin by adding it to the NOSE_PLUGINS Django setting:
NOSE_PLUGINS = [ 'django_nose_qunit.QUnitPlugin' ]
and the NOSE_ARGS Django setting:
NOSE_ARGS = [ '--with-django-qunit', ]
Add an entry to your URL configuration:
from django_nose_qunit.urls import urlpatterns as qunit_urlpatterns urlpatterns += qunit_urlpatterns
This adds new URLs of the form /qunit/*, and they return a 404 unless DEBUG is True or QUnit tests have been initialized as part of a test run.
Configure Selenium as explained in the sbo-selenium README.
Make sure MEDIA_URL is set to some non-empty string, like “/media/”. If this is not done, the live test server can occasionally get confused and treat requests for a test page as requests for static files.
Creating Unit Tests
To make nose aware of your QUnit tests, create a subclass of django_nose_qunit.QUnitTestCase in a file which would normally be searched by nose, for example my_app/test/qunit/test_case.py. It can contain as little as just the test_file attribute (a path to a QUnit test script, relative to STATIC_URL). Any script dependencies for your test script should be given as paths relative to STATIC_URL in the dependencies attribute. Paths to HTML fixture templates are listed in the html_fixtures attribute.
Running Unit Tests
Use your normal test execution command (using django-admin.py or manage.py). Execution can be restricted to one or more specified packages and/or classes as normal (“myapp”, “myapp.tests.qunit”, “myapp.tests.qunit:MyTestCase”, etc.). There is currently no support for running only a single module or test within a QUnit test script; QUnit module and test names can be arbitrary strings, which makes it difficult for the nose command line parser to handle them.
To run the QUnit tests in a regular web browser, use the runserver management command with QUNIT_DYNAMIC_REGISTRY set to True (by default, it has the same value as DEBUG). If DEBUG is False, you’ll also need to use the --insecure parameter to serve static files. You can then access a list of links to the available QUnit tests at a URL like http://localhost:8000/qunit/. This can be useful when first developing a test script and when troubleshooting failing tests.
How It Works
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size django_nose_qunit-1.6.1-py2.py3-none-any.whl (49.9 kB)||File type Wheel||Python version py2.py3||Upload date||Hashes View|
|Filename, size django-nose-qunit-1.6.1.tar.gz (44.4 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for django_nose_qunit-1.6.1-py2.py3-none-any.whl