| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-05-15 | Fixed #31395 -- Made setUpTestData enforce in-memory data isolation. | Simon Charette | |
| Since it's introduction in Django 1.8 setUpTestData has been suffering from a documented but confusing caveat due to its sharing of attributes assigned during its execution with all test instances. By keeping track of class attributes assigned during the setUpTestData phase its possible to ensure only deep copies are provided to test instances on attribute retreival and prevent manual setUp gymnastic to work around the previous lack of in-memory data isolation. Thanks Adam Johnson for the extensive review. | |||
| 2019-01-14 | Refs #28478 -- Prevented connection attempts against disallowed databases in ↵ | Simon Charette | |
| tests. Mocking connect as well as cursor methods makes sure an appropriate error message is surfaced when running a subset of test attempting to access a a disallowed database. | |||
| 2019-01-10 | Refs #28478 -- Deprecated TestCase's allow_database_queries and multi_db in ↵ | Simon Charette | |
| favor of databases. | |||
| 2016-02-13 | Fixed #11665 -- Made TestCase check deferrable constraints after each test. | Jon Dufresne | |
