oioioi.contestlogo.tests

Module Contents

Classes

ContestControllerWithoutDefaults

Contains the contest logic and rules.

ContestControllerWithDefaults

Contains the contest logic and rules.

TestProcessorsWithoutUploadedFiles

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

TestProcessorsWithUploadedFiles

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

TestUpdatedAt

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

class oioioi.contestlogo.tests.ContestControllerWithoutDefaults(contest)[source]

Bases: oioioi.programs.controllers.ProgrammingContestController

Contains the contest logic and rules.

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

default_contestlogo_url()[source]
default_contesticons_urls()[source]
class oioioi.contestlogo.tests.ContestControllerWithDefaults(contest)[source]

Bases: oioioi.programs.controllers.ProgrammingContestController

Contains the contest logic and rules.

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

default_contestlogo_url()[source]
default_contesticons_urls()[source]
class oioioi.contestlogo.tests.TestProcessorsWithoutUploadedFiles(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'][source]
_render_menu()[source]
test_without_defaults()[source]
test_with_defaults()[source]
class oioioi.contestlogo.tests.TestProcessorsWithUploadedFiles(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_logo', 'test_icon'][source]
_render_menu()[source]
test_with_defauts_and_uploaded_files()[source]
class oioioi.contestlogo.tests.TestUpdatedAt(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_contest', 'test_logo', 'test_icon'][source]
to_http_date(dt)[source]
request_file(url, update_date)[source]
test_icon_last_modified()[source]
test_logo_last_modified()[source]