oioioi.evalmgr.tests.tests

Module Contents

Classes

TestLocalJobs	Similar to TransactionTestCase, but use transaction.atomic() to achieve
SioworkersBackend
TestRemoteJobs	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestErrorBehavior	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestAsyncJobs	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestViews	Similar to TransactionTestCase, but use transaction.atomic() to achieve
AddHandlersController	Contains the contest logic and rules.
TestEval	Similar to TransactionTestCase, but use transaction.atomic() to achieve

Functions

delay_environ_wrapper(*args, **kwargs)
hunting_handler(env, **kwargs)
prepare_handler(env, **kwargs)
rest_handler(env, **kwargs)
upload_source(env, **kwargs)
compile_source(env, **kwargs)
upload_inout(env, **kwargs)
run(env, **kwargs)
_uuid()
police_handler(env, **kwargs)
corrupted_police_handler(env, **kwargs)
set_mood(env, **kwargs)
_call_transfer(environ)
_resume(saved_environ, environ)
_transfer(environ[, transfer_magic])

Attributes

hunting
police_files

oioioi.evalmgr.tests.tests.delay_environ_wrapper(*args, **kwargs)

oioioi.evalmgr.tests.tests.hunting = [['Prepare guns', 'oioioi.evalmgr.tests.tests.prepare_handler'], None, ['Rest',...

exception oioioi.evalmgr.tests.tests.HuntingException

Bases: Exception

Common base class for all non-exit exceptions.

oioioi.evalmgr.tests.tests.hunting_handler(env, **kwargs)

oioioi.evalmgr.tests.tests.prepare_handler(env, **kwargs)

oioioi.evalmgr.tests.tests.rest_handler(env, **kwargs)

class oioioi.evalmgr.tests.tests.TestLocalJobs(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_evalmgr_job()

test_cascade_job()

test_multiple_jobs()

oioioi.evalmgr.tests.tests.upload_source(env, **kwargs)

oioioi.evalmgr.tests.tests.compile_source(env, **kwargs)

oioioi.evalmgr.tests.tests.upload_inout(env, **kwargs)

oioioi.evalmgr.tests.tests.run(env, **kwargs)

class oioioi.evalmgr.tests.tests.SioworkersBackend

Bases: object

run_job(env)

oioioi.evalmgr.tests.tests._uuid()

class oioioi.evalmgr.tests.tests.TestRemoteJobs(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.

base_dir

local_source_file

remote_source_file

local_wrong_source_file

remote_wrong_source_file

binary_file

local_in_file

remote_in_file

local_out_file

remote_out_file

evaluation_recipe = [['upload source', 'oioioi.evalmgr.tests.tests.upload_source'], ['compile source',...

evaluation_env

tearDown()

Hook method for deconstructing the test fixture after testing it.

_run_with_dummy_sioworkers(testfn)

test_full_source_file_evaluation_with_dummy_sioworkers()

test_multiple_source_file_evaluation_with_dummy_sioworkers()

test_full_source_file_evaluation()

test_multiple_source_file_evaluation()

oioioi.evalmgr.tests.tests.police_files

exception oioioi.evalmgr.tests.tests.SuspectNotFoundException

Bases: Exception

Common base class for all non-exit exceptions.

oioioi.evalmgr.tests.tests.police_handler(env, **kwargs)

oioioi.evalmgr.tests.tests.corrupted_police_handler(env, **kwargs)

oioioi.evalmgr.tests.tests.set_mood(env, **kwargs)

class oioioi.evalmgr.tests.tests.TestErrorBehavior(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.

error_handlers = [['Call police', 'oioioi.evalmgr.tests.tests.police_handler'], None]

arrest = [['Call police', 'oioioi.evalmgr.tests.tests.police_handler']]

corrupted_error_handler = [['Call police', 'oioioi.evalmgr.tests.tests.corrupted_police_handler']]

test_error_behavior()

class oioioi.evalmgr.tests.tests.TestAsyncJobs(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.

transferred_environs = []

_prepare()

test_transfer_job()

test_environ_save()

test_transfer_fail()

test_job_resumed_twice()

test_saved_environ_id()

oioioi.evalmgr.tests.tests._call_transfer(environ)

oioioi.evalmgr.tests.tests._resume(saved_environ, environ)

oioioi.evalmgr.tests.tests._transfer(environ, transfer_magic=None)

class oioioi.evalmgr.tests.tests.TestViews(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', 'test_submission']

_get_admin_site()

assertStateCountEqual(state_str, count, show_response=None)

Asserts that the number of the submits with given state (state_str) that appear on the admin site is count.

assertNotPresent(state_strs)

Asserts that none of the state_strs is present on the admin page

test_admin_view()

Test if a submit shows on the list properly.

class oioioi.evalmgr.tests.tests.AddHandlersController(contest)

Bases: oioioi.programs.controllers.ProgrammingContestController

Contains the contest logic and rules.

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

class oioioi.evalmgr.tests.tests.TestEval(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', 'test_submission']

test_add_handlers()

Test if the proper handlers are added to the recipe.

test_revoke()

Test if a submit revokes properly.