:orphan:

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

.. py:module:: oioioi.exportszu.tests


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

Classes
~~~~~~~

.. autoapisummary::

   oioioi.exportszu.tests.TestSubmissionsWithUserDataCollector
   oioioi.exportszu.tests.TestFinalSubmissionsWithUserDataCollector
   oioioi.exportszu.tests.TestExportCommand
   oioioi.exportszu.tests.TestExportSubmissionsView




Attributes
~~~~~~~~~~

.. autoapisummary::

   oioioi.exportszu.tests.INDEX_HEADER


.. py:class:: TestSubmissionsWithUserDataCollector(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_submission',...

      

   .. py:method:: assert_correct_submission_data(submission_data_list)


   .. py:method:: test_default()


   .. py:method:: test_not_only_final()


   .. py:method:: test_specific_round()



.. py:class:: TestFinalSubmissionsWithUserDataCollector(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_submission',...

      

   .. py:method:: test_default()


   .. py:method:: test_not_only_final()



.. py:data:: INDEX_HEADER
   :annotation: = submission_id,user_id,username,first_name,last_name,city,school,school_city,problem_short_name,score


   

.. py:class:: TestExportCommand(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_submission',...

      

   .. py:method:: test_export()



.. py:class:: TestExportSubmissionsView(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_submission']

      

   .. py:method:: test_link_to()


   .. py:method:: test_download()