oioioi.filetracker.tests

Module Contents

Classes

TestFileField	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestFileStorage	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestStreamingMixin
TestFileStorageViews	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestFileFixtures	Similar to TransactionTestCase, but use transaction.atomic() to achieve
TestFileUtils	Similar to TransactionTestCase, but use transaction.atomic() to achieve

class oioioi.filetracker.tests.TestFileField(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_file_field()

test_filetracker_to_django_field()

test_django_to_filetracker_path()

class oioioi.filetracker.tests.TestFileStorage(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_file_storage(storage)

test_dummy_file_storage()

test_real_file_storage()

class oioioi.filetracker.tests.TestStreamingMixin

Bases: object

assertStreamingEqual(response, content)

streamingContent(response)

class oioioi.filetracker.tests.TestFileStorageViews(methodName='runTest')

Bases: oioioi.base.tests.TestCase, TestStreamingMixin

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_raw_file_view()

class oioioi.filetracker.tests.TestFileFixtures(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_file_field']

test_file_fixtures()

class oioioi.filetracker.tests.TestFileUtils(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_content_disposition()