oioioi.quizzes.tests

Module Contents

Classes

SubmitQuizMixin
TestTextInput	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestSubmission	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestScore	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestScoreRejudgeAfterNewQuestionsAdded	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestSubmissionView	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestEditQuizQuestions	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestQuizBleach	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPictures	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestQuizProblemView	Similar to TransactionTestCase, but use transaction.atomic() to achieve

class oioioi.quizzes.tests.SubmitQuizMixin

Bases: oioioi.contests.tests.SubmitMixin

submit_quiz(contest, problem_instance, answers)

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:

1. answer id

2. list of answer ids if question is multiple choice

:return response to the request

class oioioi.quizzes.tests.TestTextInput(methodName='runTest')

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.

fixtures = ['test_users', 'test_basic_contest', 'test_problem_instance', 'test_quiz_problem_with_text_input']

setUp()

Hook method for setting up the test fixture before exercising it.

test_simple_submission()

test_second_possible_answer()

test_wrong_answer()

class oioioi.quizzes.tests.TestSubmission(methodName='runTest')

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.

fixtures = ['test_users', 'test_basic_contest', 'test_quiz_problem', 'test_quiz_problem_second',...

setUp()

Hook method for setting up the test fixture before exercising it.

test_simple_submission()

test_empty_multiple_choice()

test_wrong_id()

test_submission_unanswered_question()

class oioioi.quizzes.tests.TestScore(methodName='runTest')

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_quiz_problem_second',...

test_multiple_choice_no_correct_answer_score()

test_all_answers_correct_score()

test_one_answer_incorrect_score()

class oioioi.quizzes.tests.TestScoreRejudgeAfterNewQuestionsAdded(methodName='runTest')

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.

setUp()

Hook method for setting up the test fixture before exercising it.

test_closed_added_question_no_given_answer_score()

test_open_added_question_no_given_answer_score()

class oioioi.quizzes.tests.TestSubmissionView(methodName='runTest')

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']

setUp()

Hook method for setting up the test fixture before exercising it.

test_question_report()

test_submission_score_visible()

test_diff_submission_unavailable()

class oioioi.quizzes.tests.TestEditQuizQuestions(methodName='runTest')

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']

setUp()

Hook method for setting up the test fixture before exercising it.

test_edit_quiz_questions()

class oioioi.quizzes.tests.TestQuizBleach(methodName='runTest')

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_basic_contest', 'test_quiz_bleach', 'test_problem_instance']

setUp()

Hook method for setting up the test fixture before exercising it.

test_quizbleach()

class oioioi.quizzes.tests.TestPictures(methodName='runTest')

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_basic_contest', 'test_quiz_problem_pictures', 'test_problem_instance']

setUp()

Hook method for setting up the test fixture before exercising it.

test_embedding()

test_invalid_mode()

test_access()

test_download()

class oioioi.quizzes.tests.TestQuizProblemView(methodName='runTest')

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_full_package', 'test_problem_instance',...

disabled_quiz_tabs = ['Problem statement']

allowed_quiz_tabs = ['Secret key', 'Settings']

test_quiz_tab_visibility()

test_normal_problem_tab_visibility()