oioioi.printing.tests

Module Contents

Classes

PrintingTestContestController	Contains the contest logic and rules.
TestPDFGenerator	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestPrintingView	Similar to TransactionTestCase, but use transaction.atomic() to achieve

Attributes

SAMPLE_TEXT

oioioi.printing.tests.SAMPLE_TEXT

class oioioi.printing.tests.PrintingTestContestController(contest)

Bases: oioioi.contests.controllers.ContestController

Contains the contest logic and rules.

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

can_print_files(request)

class oioioi.printing.tests.TestPDFGenerator(methodName='runTest')

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.

test_pdf_generation()

class oioioi.printing.tests.TestPrintingView(methodName='runTest')

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']

setUp()

Hook method for setting up the test fixture before exercising it.

print_file(content)

test_print()

test_page_limit()

test_file_size_limit()