Test Runner tab

Rerun Ctrl+F5

Rerun the current test session.

The process reruns always in the same console regardless of whether this console is pinned or not.

Rerun Failed Tests

Rerun all failed tests.

Toggle auto-test

Enable the autotest-like runner.

As a result, any test in the current run configuration tab restarts automatically on changing the related source code, without clicking the Rerun button .

The button is not shown for Mocha and Jest tests. To activate the auto-rerun functionality for these test runners, add the --watch flag in the Extra Mocha options/Extra Jest options field of the Run/Debug Configuration: Mocha or Run/Debug Configuration: Jest dialog respectively.

Stop and rerun

Ctrl+F5

Click this button to stop executing the current test session and have the test re-started automatically. When the test execution stops, the button toggles to Rerun  .

Stop Ctrl+F2

Terminate the current process externally by means of the standard mechanisms.

Restore Layout

Click this button to have the changes to the current layout abandoned and return to the default state.

Pin

When this button is pressed, the current tab will not be overwritten; instead, the results of the next command will be displayed in a new tab.

Show Passed

Show tests that passed successfully.

Show Ignored

Show the ignored tests in the tree view of all tests within the current run/debug configuration or test class.

Sort Alphabetically

Sort tests in alphabetical order.

Sort By Duration

Sort tests by duration.

Expand All/Collapse All

Ctrl+NumPad + Ctrl+NumPad -

Expand/collapse all nodes in the test tree view.

These buttons are only available if the tested application contains more than test case.

Previous/Next Failed Test

Ctrl+Alt+Up/Ctrl+Alt+Down

Navigate between the failed tests.

Test History

Open the list of internally saved results of test sessions. Each item is supplied with the name of the run configuration and a time stamp.

To view the results of a testing session from the WebStorm history, select the item with the suitable run configuration and time stamp. The loaded test results are shown in a new tab, and the name of the corresponding run configuration is displayed in the title bar.

To re-run the tests from the loaded session, click .

Import Tests from File

Load previously exported test results. This button opens a dialog in which you can select the required XML file with test results.

Click this cog button to access the context menu with the following options:

• Track Running Test: turn this option on to monitor execution of the current test. If a test suite contains multiple tests, the tree view of tests expands to show sequential test methods, as they are executed.

• Show Inline Statistics: turn this option on to have the statistics shown next to a test result, displaying the time used for executing each test.

• Scroll to Stack Trace: turn this option on to have the console scroll to the beginning of the trace of the last failed test.

  If you click the root node (the test package) in the tree view with this option turned off, the console will show the very beginning of the test.

  This option is helpful when a test package contains multiple test classes and test methods. If some of the tests fail, you can scroll in the console to the beginning of a stack trace of an exception or assertion.

• Open Source at Exception: use this option to explore the results of a test that fails as an error, throwing an uncaught exception.

  If you double-click the failed test class or method in the tree view with this option turned on, the respective test class or method will open in the editor, with the caret placed at the line that caused the problem.

• Navigate with Single Click: turn this option on to have the currently selected test in the tree view synchronized with the editor automatically.

• Set Auto Test Delay: point to this node to reveal the list of available delays between file saving and rerunning tests. The selected value gets the check mark.

• Select First Failed Test When Finished: turn this option on to have the first failed test automatically selected in the tree view upon completing the tests.

Test error. This status is assigned to tests that caused an exception from the tested source code.

Test failed. If at least one test receives this status, then all its parents are marked as failed.

Test ignored.

Test in progress.

Test passed successfully.

Test terminated. This status is assigned to tests that were cancelled by clicking the Stop button . If at least one test receives this status, then all unfinished tests and their parents are marked as terminated.

Up the stack trace

Ctrl+Alt+Down

Navigate up in the stack trace and have the caret jump to the corresponding location in the source code.

Down the stack trace

Ctrl+Alt+Up

Navigate down in the stack trace and have the caret jump to the corresponding location in the source code.

Use Soft Wraps

Toggle the soft wrap mode of the output.

Scroll to the end

Navigate to the bottom of the stack trace and have the caret jump to the corresponding location in the source code.

Print

Configure printing out the console output in the Print dialog that opens.

Clear All

Delete all messages for the selected test.

Run <test name>

Ctrl+Shift+F10

Run the selected test with the automatically generated run/debug configuration or choose another one from the list.

Debug <test name>

Debug the selected test with the automatically generated run/debug configuration or choose another one from the list.

Run <test name> with Coverage

Ctrl+Shift+F10

Run the selected test and collect coverage with the automatically generated run/debug configuration or choose another one from the list.

Jump to Source

F4

Choose this command to move the focus to the editor, to the definition of a test class, or a test method.

Show Source

Ctrl+Enter

Choose this command to open source code in the editor, but leave the focus with the Test Runner tab.