Changes between Initial Version and Version 1 of Ticket #23742, comment 5
- Timestamp:
- Nov 22, 2014, 5:53:54 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #23742, comment 5
initial v1 1 Update: rebased [https://github.com/django/django/pull/3543 the pull], split some line breaking fixes into another commit, moved the new test to a better place and made the optionreverse test cases within test classes (as defined in [https://docs.djangoproject.com/en/dev/topics/testing/overview/#order-in-which-tests-are-executed testing docs]), but leave the classes in the working order.1 Update: rebased [https://github.com/django/django/pull/3543 the pull], split some line breaking fixes into another commit, moved the new test to a better place, made the option available with `manage.py test` and made it reverse test cases within test classes (as defined in [https://docs.djangoproject.com/en/dev/topics/testing/overview/#order-in-which-tests-are-executed testing docs]), but leave the classes in the working order. 2 2 3 3 As [https://github.com/wrwrwr/django/commit/00a5eebf2e798a4cc53b18e77aacefcef2efe482#commitcomment-8682804 noticed] by Preston, there is actually another level of reversing to consider. First, reversing labels should always work. Secondly, Django sorts tests into `django.TestCase`, `django.SimpleTestCase` and `unittest.TestCase`, these groups shouldn't be probably reversed as the order is guaranteed in documentation. Thirdly, cases within groups should be independent. And lastly, test methods would better be independent too (though there can be some reasonable exceptions).