75π
A tenet of unit-testing is that each test should be independent of all others.
If in your case the code in testTestA must come before testTestB, then you could
combine both into one test:
def testTestA_and_TestB(self):
# test code from testTestA
...
# test code from testTestB
or, perhaps better would be
def TestA(self):
# test code
def TestB(self):
# test code
def test_A_then_B(self):
self.TestA()
self.TestB()
The Test
class only tests those methods who name begins with a lower-case test...
.
So you can put in extra helper methods TestA
and TestB
which wonβt get run unless you explicitly call them.
12π
As far as I know, there is no way to order tests other than rename them. Could you explain why you need to run test cases in the specific order? In unit testing it usually considered as bad practice since it means that your cases are not independent.
- [Django]-Playframework and Django
- [Django]-Django model blank=False does not work?
- [Django]-LEFT JOIN Django ORM
8π
To update on the topic (from documentation):
Order in which tests are executed
In order to guarantee that all
TestCase
code starts with a clean
database, the Django test runner reorders tests in the following way:
- All
TestCase
subclasses are run first.- Then, all other Django-based
tests (test cases based onSimpleTestCase
, including
TransactionTestCase
) are run with no particular ordering guaranteed
nor enforced among them.- Then any other
unittest.TestCase
tests
(includingdoctests
) that may alter the database without restoring it
to its original state are run.Note: The new ordering of tests may reveal unexpected dependencies on test
case ordering. This is the case with doctests that relied on state
left in the database by a givenTransactionTestCase
test, they must be
updated to be able to run independently.
- [Django]-How to upload multiple files in django rest framework
- [Django]-Generating PDFs from SVG input
- [Django]-No Module named django.core