oioioi.quizzes.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 |
|
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 |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
|
Similar to TransactionTestCase, but use transaction.atomic() to achieve |
- class oioioi.quizzes.tests.SubmitQuizMixin[source]¶
Bases:
oioioi.contests.tests.SubmitMixin
- submit_quiz(contest, problem_instance, answers)[source]¶
Submits a quiz with given answer :param contest: in what contest to submit :param problem_instance: indicates which quiz to submit :param answers: dictionary mapping question ids to:
answer id
list of answer ids if question is multiple choice
:return response to the request
- class oioioi.quizzes.tests.TestTextInput(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
,SubmitQuizMixin
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.quizzes.tests.TestSubmission(methodName='runTest')[source]¶
Bases:
oioioi.base.tests.TestCase
,SubmitQuizMixin
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.quizzes.tests.TestScore(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.quizzes.tests.TestScoreRejudgeAfterNewQuestionsAdded(methodName='runTest')[source]¶
Bases:
TestScore
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.quizzes.tests.TestSubmissionView(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.
- fixtures = ['test_users', 'test_contest', 'test_quiz_problem', 'test_problem_instance', 'test_quiz_submission'][source]¶
- class oioioi.quizzes.tests.TestEditQuizQuestions(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.quizzes.tests.TestQuizBleach(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.quizzes.tests.TestPictures(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.quizzes.tests.TestQuizProblemView(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.