Part of twisted.trial.reporter View Source View In Hierarchy
Implements interfaces: twisted.trial.itrial.IReporter
|Method||done||Record that the entire test suite run is finished.|
|Method||shouldStop||Whether or not the test runner should stop running tests.|
|Method||stop||Signal that the test runner should stop running tests.|
|Method||wasSuccessful||Has the test run been successful so far?|
|Method||addExpectedFailure||Record an expected failure from a test.|
|Method||addUnexpectedSuccess||Record an unexpected success.|
|Instance Variable||_subunit||The subunit protocol client that we are wrapping.|
|Instance Variable||_successful||An internal variable, used to track whether we have received only successful results.|
|Parameters||stream||A file-like object representing the stream to print output to. Defaults to stdout.|
|tbformat||The format for tracebacks. Ignored, since subunit always uses Python's standard format.|
|realtime||Whether or not to print exceptions in the middle of the test results. Ignored, since subunit always does this.|
|publisher||The log publisher which will be preserved for reporting events. Ignored, as it's not relevant to subunit.|
We do nothing, since a summary clause is irrelevant to the subunit protocol.
testwas skipped for
Some versions of subunit don't have support for addSkip. In those cases, the skip is reported as a success.
|Parameters||test||A unittest-compatible |
|reason||The reason for it being skipped. The |
Some versions of subunit do not implement this. For those versions, we record a success.