![]() ![]() We modified an existing test but didn't dive into testing. 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.We briefly saw the Jest test runner in Project Setup. Set Auto Test Delay: point to this node to reveal the list of available delays between file saving and rerunning tests. Navigate with Single Click: turn this option on to have the currently selected test in the tree view synchronized with the editor automatically. 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. Open Source at Exception: use this option to explore the results of a test that fails as an error, throwing an uncaught exception. If some of the tests fail, you can scroll in the console to the beginning of a stack trace of an exception or assertion. This option is helpful when a test package contains multiple test classes and test methods. ![]() 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. Scroll to Stack Trace: turn this option on to have the console scroll to the beginning of the trace of the last failed test. 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. If a test suite contains multiple tests, the tree view of tests expands to show sequential test methods, as they are executed. Track Running Test: turn this option on to monitor execution of the current test. This button opens a dialog in which you can select the required XML file with test results.Ĭlick this cog button to access the context menu with the following options: To re-run the tests from the loaded session, click. 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 view the results of a testing session from the WebStorm history, select the item with the suitable run configuration and time stamp. Each item is supplied with the name of the run configuration and a time stamp. Open the list of internally saved results of test sessions. These buttons are only available if the tested application contains more than test case. Show the ignored tests in the tree view of all tests within the current run/debug configuration or test class.Įxpand/collapse all nodes in the test tree view. 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. Terminate the current process externally by means of the standard mechanisms.Ĭlick this button to have the changes to the current layout abandoned and return to the default state. When the test execution stops, the button toggles to Rerun. 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.Ĭlick this button to stop executing the current test session and have the test re-started automatically. The button is not shown for Mocha and Jest tests. The process reruns always in the same console regardless of whether this console is pinned or not.Īs a result, any test in the current run configuration tab restarts automatically on changing the related source code, without clicking the Rerun button. Rerunning failed tests is available only for Karma, Jest, or Mocha. The inline statistics show the list of executed tests with the execution time of each test. The output pane shows the output of the current test suit. Some of the commands are duplicated on the context menus of the test tree nodes. The testing toolbar provides controls that enable you to monitor the tests and analyze results. Double-click a node to open the respective test class or test method in the editor. The status of each test is indicated by an icon. The leaf nodes represent the individual tests. ![]() ![]() The nested nodes represent the hierarchy of test suites and test cases. The root node represents the test selected to run. The left-hand pane shows the tree view of all tests within the current run/debug configuration. The run toolbar is almost the same as that for the Run tool window, but features testing-specific buttons. The Test Runner tab opens in the Run tool window when a testing session begins, and features the same toolbar buttons. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |