Test Runner Tab
In this section:
- The Run toolbar is almost the same as that for the Run tool window, but features testing-specific buttons.
- The left-hand pane shows the tree view of all tests within the current run/debug configuration.
- The root node represents the test selected to run.
- The nested nodes represent the hierarchy of test suites and test cases.
- The leaf nodes represent the individual tests.
The status of each test is indicated by an icon. Double-click a node to open the respective test class or test method in the editor.
- The testing toolbar provides controls that enable you to monitor the tests and analyze results. Some of the commands are duplicated on the context menus of the test tree nodes.
- The Output pane shows the output of the current test suit.
- The inline statistics show the list of executed tests with the execution time of each test.
- The color of the status bar indicates whether the tests have passed successfully. If at least one of the tests fails, the status bar turns red.
|Item||Tooltip and Shortcut||Description|
|Click this button to rerun the current process. |
The process reruns always in the same console regardless of whether this console is pinned or not.
|Toggle auto-test|| Press this toggle-button to turn on 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
|Click this button to terminate the current process externally by means of the standard mechanisms.|
|Restore Layout||Click this button to 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.|
|Ctrl+Shift+F4||Click this button to close the selected tab of the Run tool window and terminate the current process.|
|F1||Click this button to show reference.|
|Item||Tooltip and Shortcut||Description|
|Show Passed||Click this button to show tests that passed successfully.|
|Show Ignored||Click this button to show the ignored tests in the tree view of all tests within the current run/debug configuration or test class.|
|Sort alphabetically||Click this button to sort tests in alphabetical order.|
|Sort by duration||Click this button to sort tests by duration.|
|Expand All/Collapse All|
Ctrl+NumPad Plus Ctrl+NumPad -
|Click these buttons to have all nodes in the tree view of tests expanded. |
These buttons are only available if the tested application contains more than test case.
|Previous/Next Failed Test|
|Click these buttons to navigate between the failed tests.|
|Import Test Results||Click this button to view the test results that you previously saved in an XML file or the results that RubyMine has kept in its internal history. The pop-up menu that opens shows a list of internally saved results of test sessions, each item is supplied with the name of the run configuration and a time stamp. |
|Click this cog button to access the context menu with the following options: |
Test status icons
|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.|
This pane shows output of each test, generated at runtime, including all the messages sent to the output stream, and the error messages. The following table shows the toolbar buttons and context menu commands available for the Output pane.
|Up the Stack Trace|
|Click this button to navigate up in the stack trace and have the cursor jump to the corresponding location in the source code.|
|Down the Stack Trace|
|Click this button to navigate down in the stack trace and have the cursor jump to the corresponding location in the source code.|
|Use Soft Wraps||Click this button to toggle the soft wrap mode of the output.|
|Scroll to the end||Click this button to navigate to the bottom of the stack trace and have the cursor jump to the corresponding location in the source code.|
|Click this button to configure printing out the console output in the Print dialog box that opens.|
|Clear All||Choose this item on the context menu to have all messages for the selected test deleted.|
|Copy Content||Ctrl+C||Choose this item on the context menu to have the current contents of the Output pane placed to the Clipboard.|
|Compare with Clipboard||Choose this item on the context menu to invoke the Differences Viewer for Files which shows the current contents of the Clipboard in the left-hand pane and the contents of the Output pane for the selected test in the right-hand pane.|
Context menu commands