oioioi.oi.tests

Module Contents

Classes

TestOIAdmin	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestOIRegistration	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestOIViews	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestSchoolAdding	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestSchoolAdmin	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestSchoolMerging	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestOISubmit	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestOIOnsiteSubmit	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestIgnoringCE	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestUserInfo	Similar to TransactionTestCase, but use transaction.atomic() to achieve

class oioioi.oi.tests.TestOIAdmin(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_oi_registration', 'test_permissions']

test_admin_menu()

test_schools_import()

test_safe_exec_mode()

test_terms_accepted_phrase_inline_admin_permissions()

test_terms_accepted_phrase_inline_edit_restrictions()

class oioioi.oi.tests.TestOIRegistration(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_schools', 'test_terms_accepted_phrase']

setUp()

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

test_participants_accounts_menu()

test_participants_unregister_forbidden()

test_default_terms_accepted_phrase()

test_participants_registration()

test_registration_with_new_school()

class oioioi.oi.tests.TestOIViews(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', 'test_submission']

test_contest_visibility()

test_contest_access()

test_ranking_access()

class oioioi.oi.tests.TestSchoolAdding(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_schools']

setUp()

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

test_schools_similar_view()

class oioioi.oi.tests.TestSchoolAdmin(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_schools']

test_schools_similar_finding()

class oioioi.oi.tests.TestSchoolMerging(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_schools']

_call_admin_merge_action(schools_pk_list)

test_schools_merging_unsuccessfull()

class oioioi.oi.tests.TestOISubmit(methodName='runTest')

Bases: oioioi.base.tests.TestCase, oioioi.programs.tests.SubmitFileMixin

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_submit_permissions()

class oioioi.oi.tests.TestOIOnsiteSubmit(methodName='runTest')

Bases: oioioi.base.tests.TestCase, oioioi.programs.tests.SubmitFileMixin

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_submit_permissions()

class oioioi.oi.tests.TestIgnoringCE(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', 'test_submission',...

_test(controller_name)

test_all_oi_style_contests()

class oioioi.oi.tests.TestUserInfo(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_schools', 'test_permissions']

test_user_info_page()