ReadonlycontrollerReadonlyidReadonlyisWhether the test run will be persisted across reloads by the editor.
ReadonlynameThe 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.
An event fired when the editor is no longer interested in data associated with the test run.
A cancellation token which will be triggered when the test run is canceled from the UI.
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).
Signals the end of the test run. Any tests included in the run whose states have not been updated will have their state reset.
Indicates a test is queued for later execution.
Test item to update.
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.
Optionalduration: numberHow long the test took to execute, in milliseconds.
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.
Optionalduration: numberHow long the test took to execute, in milliseconds.
Indicates a test has passed.
Test item to update.
Optionalduration: numberHow long the test took to execute, in milliseconds.
A TestRun represents an in-progress or completed test run and provides methods to report the state of individual tests in the run.