oioioi.problems.tests.test_tags
¶
Module Contents¶
Classes¶
Abstract base class with getting url utility for algorithm tags proposal tests. |
|
Abstract base class with getting url utility for algorithm tags proposal tests. |
|
Abstract base class with getting url utility for algorithm tags proposal tests. |
|
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 |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
- class oioioi.problems.tests.test_tags.TestAlgorithmTagsProposalHintsBase(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
Abstract base class with getting url utility for algorithm tags proposal tests.
- class oioioi.problems.tests.test_tags.TestAlgorithmTagsProposalHintsEnglish(methodName='runTest')[source]¶
Bases:
TestAlgorithmTagsProposalHintsBase
Abstract base class with getting url utility for algorithm tags proposal tests.
- class oioioi.problems.tests.test_tags.TestAlgorithmTagsProposalHintsPolish(methodName='runTest')[source]¶
Bases:
TestAlgorithmTagsProposalHintsBase
Abstract base class with getting url utility for algorithm tags proposal tests.
- class oioioi.problems.tests.test_tags.TestAlgorithmTagLabel(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.test_tags.TestSaveProposals(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.test_tags.TestProblemSearchOrigin(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
,oioioi.problems.tests.utilities.AssertContainsOnlyMixin
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.test_tags.TestProblemSearchHintsTags(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
,oioioi.problems.tests.utilities.AssertContainsOnlyMixin
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.