Each Answer to this Q is separated by one/two green lines.
More specifically, what are the use cases for each?
What I’ve understood so far:
- This method runs once, before all the tests in a test class
- This method runs once if the DB has transaction support. Otherwise it runs before each test.
- This method runs before each test in a test class.
From the understanding I mentioned above, it seems setUpTestData lies in the area between setUpClass and setUp. Why do we need a class level method for setuUpTestData while the same effect could be achieved by either
setUp or a combination of the both?
EDIT: Update/Correction after Alasdair’s comment
setUpClassis used to perform class-wide initialization/configuration (e.g. creating connections, loading webdrivers). When using
setUpClassfor instance to open database connection/session you can use
tearDownClassto close them.
setUpClassis called once for the TestCase before running any of the tests. Similarly
tearDownClassis called after all the tests have run.
Note from documentation:
SimpleTestCase and its subclasses (e.g. TestCase, …) rely on setUpClass() and tearDownClass() to perform some class-wide initialization (e.g. overriding settings). If you need to override those methods, don’t forget to call the super implementation:
setUpTestDatais used to create initial test data per TestCase. This method is called by TestCase.setUpClass() (src)
setUpTestDatais called once for TestCase, as explained in documentation. In case databases does not support transactions,
setUpTestDatawill be called before each test run (thanks @Alasdair for correcting me)
setUpwill be called before each test run, and should be used to prepare test dataset for each test run.
setUpTestData allows for test performance improvement, be aware that change to this data in tests will persist between different test runs. If needs to be reloaded it can be done so from
If database used for running tests does not support transactions, performance improvement is negated (as
setUpTestData will be called before each test run)