:orphan:

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

.. py:module:: oioioi.contestlogo.tests


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

Classes
~~~~~~~

.. autoapisummary::

   oioioi.contestlogo.tests.ContestControllerWithoutDefaults
   oioioi.contestlogo.tests.ContestControllerWithDefaults
   oioioi.contestlogo.tests.TestProcessorsWithoutUploadedFiles
   oioioi.contestlogo.tests.TestProcessorsWithUploadedFiles
   oioioi.contestlogo.tests.TestUpdatedAt




.. py:class:: ContestControllerWithoutDefaults(contest)

   Bases: :py:obj:`oioioi.programs.controllers.ProgrammingContestController`

   Contains the contest logic and rules.

   This is the computerized implementation of the contest's official
   rules.

   .. py:method:: default_contestlogo_url()


   .. py:method:: default_contesticons_urls()



.. py:class:: ContestControllerWithDefaults(contest)

   Bases: :py:obj:`oioioi.programs.controllers.ProgrammingContestController`

   Contains the contest logic and rules.

   This is the computerized implementation of the contest's official
   rules.

   .. py:method:: default_contestlogo_url()


   .. py:method:: default_contesticons_urls()



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

      

   .. py:method:: _render_menu()


   .. py:method:: test_without_defaults()


   .. py:method:: test_with_defaults()



.. py:class:: TestProcessorsWithUploadedFiles(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_logo', 'test_icon']

      

   .. py:method:: _render_menu()


   .. py:method:: test_with_defauts_and_uploaded_files()



.. py:class:: TestUpdatedAt(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_contest', 'test_logo', 'test_icon']

      

   .. py:method:: to_http_date(dt)


   .. py:method:: request_file(url, update_date)


   .. py:method:: test_icon_last_modified()


   .. py:method:: test_logo_last_modified()