oioioi.pa.tests

Module Contents

Classes

TestPAScore	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPARoundTimes	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPARanking	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPARegistration	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPAScorer	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPAResults	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPADivisions	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPAContestInfo	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPASafeExecModes	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPAAdmin	Similar to TransactionTestCase, but use transaction.atomic() to achieve

class oioioi.pa.tests.TestPAScore(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.

test_score_distribution()

test_pa_score()

class oioioi.pa.tests.TestPARoundTimes(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_pa_contest']

test_round_states()

class oioioi.pa.tests.TestPARanking(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_pa_contest']

_ranking_url(key)

test_divisions()

test_no_zero_scores_in_ranking()

test_ranking_ordering()

class oioioi.pa.tests.TestPARegistration(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_terms_accepted_phrase']

setUp()

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

test_default_terms_accepted_phrase()

test_participants_registration()

test_contest_info()

class oioioi.pa.tests.TestPAScorer(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.

t_results_ok = [None, None, None]

t_expected_ok = [None, None, None]

t_results_wrong = [None, None]

t_expected_wrong = [None, None]

test_pa_test_scorer()

class oioioi.pa.tests.TestPAResults(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_pa_contest']

test_pa_user_results()

class oioioi.pa.tests.TestPADivisions(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_prolem_upload()

class oioioi.pa.tests.TestPAContestInfo(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_pa_contest']

test_contest_info_anonymous()

test_cross_origin()

class oioioi.pa.tests.TestPASafeExecModes(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_pa_contests_safe_exec_mode']

test_pa_quals_controller_safe_exec_mode()

test_pa_finals_controller_safe_exec_mode()

class oioioi.pa.tests.TestPAAdmin(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_pa_registration', 'test_permissions']

setUp()

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

test_terms_accepted_phrase_inline_admin_permissions()

test_terms_accepted_phrase_inline_edit_restrictions()