oioioi.problems.tests.tests
¶
Module Contents¶
Classes¶
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
|
TestCase for Django Migrations |
|
TestCase for Django Migrations |
- class oioioi.problems.tests.tests.TestModels(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
Similar to TransactionTestCase, but use transaction.atomic() to achieve test isolation.
In most situations, TestCase should be preferred to TransactionTestCase as it allows faster execution. However, there are some situations where using TransactionTestCase might be necessary (e.g. testing some transactional behavior).
On database backends with no transaction support, TestCase behaves as TransactionTestCase.
- class oioioi.problems.tests.tests.TestProblemsharing(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
Similar to TransactionTestCase, but use transaction.atomic() to achieve test isolation.
In most situations, TestCase should be preferred to TransactionTestCase as it allows faster execution. However, there are some situations where using TransactionTestCase might be necessary (e.g. testing some transactional behavior).
On database backends with no transaction support, TestCase behaves as TransactionTestCase.
Bases:
oioioi.base.tests.TestCase
Similar to TransactionTestCase, but use transaction.atomic() to achieve test isolation.
In most situations, TestCase should be preferred to TransactionTestCase as it allows faster execution. However, there are some situations where using TransactionTestCase might be necessary (e.g. testing some transactional behavior).
On database backends with no transaction support, TestCase behaves as TransactionTestCase.
- class oioioi.problems.tests.tests.TestVisibilityMigration(methodName='runTest')[source]¶
Bases:
oioioi.base.utils.test_migrations.TestCaseMigrations
TestCase for Django Migrations
migrate_from, migrate_to should be Django migration names of tested app setUpBeforeMigration(self, apps) method will be called before migrations are applied
source: https://www.caktusgroup.com/blog/2016/02/02/writing-unit-tests-django-migrations/
- class oioioi.problems.tests.tests.TestVisibilityMigrationReverse(methodName='runTest')[source]¶
Bases:
oioioi.base.utils.test_migrations.TestCaseMigrations
TestCase for Django Migrations
migrate_from, migrate_to should be Django migration names of tested app setUpBeforeMigration(self, apps) method will be called before migrations are applied
source: https://www.caktusgroup.com/blog/2016/02/02/writing-unit-tests-django-migrations/