oioioi.questions.tests

Module Contents

Classes

TestContestControllerMixin

TestQuestions

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

TestAllMessagesView

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

TestUserInfo

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

class oioioi.questions.tests.TestContestControllerMixin[source]

Bases: object

users_to_receive_public_message_notification()[source]
class oioioi.questions.tests.TestQuestions(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_full_package', 'test_problem_instance', 'test_messages',...[source]
test_visibility()[source]
test_pub_date()[source]
test_user_date()[source]
test_visible_messages()[source]
test_new_labels()[source]
check_unread_num(num)[source]
mark_read(message_id)[source]
mark_unread(message_id)[source]
test_mark_read()[source]
test_ask_and_reply()[source]
test_reply_notification()[source]
test_public_message_notification()[source]
test_filtering()[source]
test_authors_list()[source]
test_change_category()[source]
test_change_denied()[source]
test_reply_templates()[source]
test_check_new_messages()[source]
test_message_type_filter()[source]
test_candidate_notifications()[source]
test_unescaped()[source]
test_mailnotify()[source]
test_unseen_mail_notifications()[source]

Test whether the notifications are correctly not sent for messages which are not visible to the user

class oioioi.questions.tests.TestAllMessagesView(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_full_package', 'test_problem_instance', 'test_messages',...[source]
test_visible_messages()[source]
test_marking_as_read()[source]
test_marking_as_needs_reply()[source]
test_messages_ordering()[source]
test_filter_presence()[source]
class oioioi.questions.tests.TestUserInfo(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_full_package', 'test_problem_instance', 'test_messages',...[source]
test_user_info_page()[source]