lp:~zyga/django-testscenarios/0.6

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:django-testscenarios at revision 23

Linaro Validation Team: Pending requested 2011-05-23

Diff: 431 lines (+160/-56)

15 files modified

django_testproject/settings.py (+16/-14)
django_testproject/templates/django_testproject/base.html (+10/-0)
django_testproject/templates/registration/base.html (+4/-0)
django_testproject/templates/registration/logged_out.html (+3/-0)
django_testproject/templates/registration/login.html (+25/-0)
django_testproject/tests.py (+50/-3)
django_testscenarios/__init__.py (+17/-0)
django_testscenarios/models.py (+1/-1)
django_testscenarios/test_project/__init__.py (+1/-1)
django_testscenarios/test_project/manage.py (+2/-2)
django_testscenarios/test_project/settings.py (+2/-6)
django_testscenarios/test_project/tests.py (+6/-2)
django_testscenarios/tests.py (+6/-6)
django_testscenarios/ubertest.py (+5/-6)
setup.py (+12/-15)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

27. By Zygmunt Krynicki on 2011-05-23

Bump version to 0.6

26. By Zygmunt Krynicki on 2011-05-23

Leave for django to decide what to run when full-testing is requested

25. By Zygmunt Krynicki on 2011-05-23

Add ability to run all tests via run_test() and run_test_for()

24. By Zygmunt Krynicki on 2011-05-23

Merge with trunk

23. By Zygmunt Krynicki on 2011-05-23

Reorganize to be compatible with django_testproject again, bump copyright headers, update setup.py, fix pep8 issues

Sorry bzr ci -i (interactive plugin) is broken on bzr 2.4 beta

22. By Zygmunt Krynicki on 2011-05-18

Fix pep8 issues in settings.py and add django_testproject/templates to TEMPLATES_DIR

21. By Zygmunt Krynicki on 2011-05-18

Add templates that allow test projects to use minimal features from django.contrib.auth

20. By Zygmunt Krynicki on 2011-05-18

Add copyright header, add run_tests_for

Previously run_tests hard-coded the location of DJANGO_SETTINGS_MODULE, this
proved a bad decision due to unfortunate interactions with path altering
modules and Django fork-based double import of the actual settings module.

To fix this I introduce a new function run_tests_for() that allows the caller
to explicitly provide the settings module for their application. This allows
for fully qualified (no more relative imports please) module as settings.

19. By Zygmunt Krynicki on 2011-01-19

Fix logic bug in previous release

18. By Zygmunt Krynicki on 2011-01-19

Add an ability to test more than one application with django_testproject.tests.run_tests