common.test package¶
Subpackages¶
- common.test.database package
- common.test.functional package
- Submodules
- common.test.functional.Environment_test module
- common.test.functional.Error_test module
- common.test.functional.OptionsParser_test module
- common.test.functional.Pipeline_test module
- common.test.functional.Processor_test module
- common.test.functional.ShellCommand_test module
- common.test.functional.URL_test module
- common.test.functional.datetime_test module
- common.test.functional.import_everything_test module
- common.test.functional.mathematical_test module
- common.test.functional.md5sum_test module
- common.test.functional.mpfit_test module
- common.test.functional.typed_list_test module
- common.test.functional.utilities_test module
- Module contents
- common.test.services package
Submodules¶
common.test.PersistentTest module¶
common.test.multicasetest module¶
-
class
common.test.multicasetest.
TestMultipleCases
(methodName='runTest')¶ Bases:
unittest.case.TestCase
A class whose instances test multiple cases.
By default, the test code itself should be placed in a method named ‘runTest’.
If the fixture may be used for many test cases, create as many test methods as are needed. When instantiating such a TestCase subclass, specify in the constructor arguments the name of the test method that the instance is to execute.
Test authors should subclass TestCase for their own tests. Construction and deconstruction of the test’s environment (‘fixture’) can be implemented by overriding the ‘setUp’ and ‘tearDown’ methods respectively.
Instances should define an iterable atribute ‘cases’. The test methods will be called once for each item in self.cases. Each case may generate its own failure or error. Therefore each test method may generate multiple failures/errors. A test method is deemed to have passed succesfully if none of the cases genereated an error
The cases attribute can be generated at class definition time, at initialization time or in the setUp method
If it is necessary to override the __init__ method, the base class __init__ method must always be called. It is important that subclasses should not change the signature of their __init__ method, since instances of the classes are instantiated automatically by parts of the framework in order to be run. Hence, the __init__ method should not be changed to pass a list of cases to the instance
-
cases
= None¶
-
shortDescription
()¶ return short description of the test, per error case this is stored in self._testMethodErrors
-