The human-readable name of the run. This can be used to disambiguate multiple sets of results in a test run. It is useful if tests are run across multiple platforms, for example.
A cancellation token which will be triggered when the test run is canceled from the UI.
Whether the test run will be persisted across reloads by the editor.
Indicates a test is queued for later execution.
Test item to update.
Indicates a test has started running.
Test item to update.
Indicates a test has been skipped.
Test item to update.
Indicates a test has failed. You should pass one or more TestMessages to describe the failure.
Test item to update.
Messages associated with the test failure.
How long the test took to execute, in milliseconds.
Indicates a test has errored. You should pass one or more TestMessages to describe the failure. This differs from the "failed" state in that it indicates a test that couldn't be executed at all, from a compilation error for example.
Test item to update.
Messages associated with the test failure.
How long the test took to execute, in milliseconds.
Indicates a test has passed.
Test item to update.
How long the test took to execute, in milliseconds.
Appends raw output from the test runner. On the user's request, the
output will be displayed in a terminal. ANSI escape sequences,
such as colors and text styles, are supported. New lines must be given
as CRLF (\r\n) rather than LF (\n).
Output text to append.
Indicate that the output was logged at the given location.
Test item to associate the output with.
Signals the end of the test run. Any tests included in the run whose states have not been updated will have their state reset.
A TestRun represents an in-progress or completed test run and provides methods to report the state of individual tests in the run.