:orphan:

:py:mod:`oioioi.questions.tests`
================================

.. py:module:: oioioi.questions.tests


Module Contents
---------------

Classes
~~~~~~~

.. autoapisummary::

   oioioi.questions.tests.TestContestControllerMixin
   oioioi.questions.tests.TestQuestions
   oioioi.questions.tests.TestAllMessagesView
   oioioi.questions.tests.TestUserInfo




.. py:class:: TestContestControllerMixin

   Bases: :py:obj:`object`

   .. py:method:: users_to_receive_public_message_notification()



.. py:class:: TestQuestions(methodName='runTest')

   Bases: :py:obj:`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.

   .. py:attribute:: fixtures
      :annotation: = ['test_users', 'test_contest', 'test_full_package', 'test_problem_instance', 'test_messages',...

      

   .. py:method:: test_visibility()


   .. py:method:: test_pub_date()


   .. py:method:: test_user_date()


   .. py:method:: test_visible_messages()


   .. py:method:: test_new_labels()


   .. py:method:: check_unread_num(num)


   .. py:method:: mark_read(message_id)


   .. py:method:: mark_unread(message_id)


   .. py:method:: test_mark_read()


   .. py:method:: test_ask_and_reply()


   .. py:method:: test_reply_notification()


   .. py:method:: test_public_message_notification()


   .. py:method:: test_filtering()


   .. py:method:: test_authors_list()


   .. py:method:: test_change_category()


   .. py:method:: test_change_denied()


   .. py:method:: test_reply_templates()


   .. py:method:: test_check_new_messages()


   .. py:method:: test_message_type_filter()


   .. py:method:: test_candidate_notifications()


   .. py:method:: test_unescaped()


   .. py:method:: test_mailnotify()


   .. py:method:: test_unseen_mail_notifications()

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



.. py:class:: TestAllMessagesView(methodName='runTest')

   Bases: :py:obj:`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.

   .. py:attribute:: fixtures
      :annotation: = ['test_users', 'test_contest', 'test_full_package', 'test_problem_instance', 'test_messages',...

      

   .. py:method:: test_visible_messages()


   .. py:method:: test_marking_as_read()


   .. py:method:: test_marking_as_needs_reply()


   .. py:method:: test_messages_ordering()


   .. py:method:: test_filter_presence()



.. py:class:: TestUserInfo(methodName='runTest')

   Bases: :py:obj:`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.

   .. py:attribute:: fixtures
      :annotation: = ['test_users', 'test_contest', 'test_full_package', 'test_problem_instance', 'test_messages',...

      

   .. py:method:: test_user_info_page()