twisted.trial.reporter.TestResult(pyunit.TestResult, object)class documentation
twisted.trial.reporterView Source (View In Hierarchy)
Implements interfaces: twisted.trial.itrial.IReporter
Accumulates the results of several
|Instance Variable||successes||count the number of successes achieved by the test run. (type:
|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||wasSuccessful||Report whether or not this test suite was successful or not.|
|Method||done||The test suite has finished running.|
Report that the given test was skipped.
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.
Report that the given test succeeded against expectations.
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.
Report that the given test failed, and was expected to do so.
In Trial, tests can be marked 'todo'. That is, they are expected to fail.
Report whether or not this test suite was successful or not.
The behaviour of this method changed in
pyunit in Python 3.4 to
fail if there are any errors, failures, or unexpected successes. Previous
to 3.4, it was only if there were errors or failures. This method
implements the old behaviour for backwards compatibility reasons, checking
just for errors and failures.
|Returns|| (type: |