oioioi.oisubmit.tests

Module Contents

Classes

OISubmitFileMixin
TestOISubmitSubmission	Similar to TransactionTestCase, but use transaction.atomic() to achieve

class oioioi.oisubmit.tests.OISubmitFileMixin

Bases: object

submit_file(contest, pi_short_name, localtime=None, siotime=None, magickey='', file_size=1024, file_name='submission.cpp')

_assertSubmitted(response, submission_number)

_assertNotSubmitted(response, submission_number)

_assertSuspected(response, submission_number, suspected_number, reason)

_assertNotSuspected(response, submission_number, suspected_number)

_assertFormError(response, submission_number, error)

class oioioi.oisubmit.tests.TestOISubmitSubmission(methodName='runTest')

Bases: oioioi.base.tests.TestCase, OISubmitFileMixin

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

setUp()

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

test_simple_submission()

test_huge_submission()

test_size_limit_accuracy()

test_submissions_limitation()

_assertUnsupportedExtension(contest, pi, name, ext)

test_extension_checking()

test_submission_form()