Part of twisted.trial.reporter View Source View In Hierarchy
Known subclasses: twisted.trial._dist.workerreporter.WorkerReporter, twisted.trial.reporter.Reporter
twisted.trial.unittest.TestCase
s.Instance Variable | successes | count the number of successes achieved by the test run. (type: int ) |
Method | __init__ | Undocumented |
Method | __repr__ | Undocumented |
Method | startTest | This must be called before the given test is commenced. |
Method | stopTest | This must be called after the given test is completed. |
Method | addFailure | Report a failed assertion for the given test. |
Method | addError | Report an error that occurred while running the given test. |
Method | addSkip | Report that the given test was skipped. |
Method | addUnexpectedSuccess | Report that the given test succeeded against expectations. |
Method | addExpectedFailure | Report that the given test failed, and was expected to do so. |
Method | addSuccess | Report that the given test succeeded. |
Method | upDownError | Undocumented |
Method | cleanupErrors | Report an error that occurred during the cleanup between tests. |
Method | startSuite | Undocumented |
Method | endSuite | Undocumented |
Method | done | The test suite has finished running. |
Method | _getTime | Undocumented |
Method | _getFailure | Convert a sys.exc_info() -style tuple to a Failure , if
necessary. |
In Trial, tests can be 'skipped'. Tests are skipped mostly because there is some platform or configuration issue that prevents them from being run correctly.
In Trial, tests can be marked 'todo'. That is, they are expected to fail. When a test that is expected to fail instead succeeds, it should call this method to report the unexpected success.
In Trial, tests can be marked 'todo'. That is, they are expected to fail.