oioioi.dashboard.tests¶
Module Contents¶
Classes¶
Contains the contest logic and rules. |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
- class oioioi.dashboard.tests.PublicMessageContestController(contest)[source]¶
Bases:
oioioi.programs.controllers.ProgrammingContestControllerContains the contest logic and rules.
This is the computerized implementation of the contest’s official rules.
- dashboard_message = 'Test public message'¶
- class oioioi.dashboard.tests.TestDashboardMessage(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.tests.TestPublicMessageSimilar 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.
- model¶
- button_viewname = 'contest_dashboard'¶
- edit_viewname = 'dashboard_message_edit'¶
- viewname = 'contest_dashboard'¶
- controller_name = 'oioioi.dashboard.tests.PublicMessageContestController'¶
- class oioioi.dashboard.tests.TestMessagesSection(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCaseSimilar 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.
- fixtures = ['test_users', 'test_contest', 'test_full_package', 'test_problem_instance', 'test_messages']¶