-js.testing.jest.navigate=Now we can see the {0} tool window with the test results and a stack trace for the failed tests coming from a test runner in it. Apart from simply tracking the test progress, you can do a lot of other things here. You can rerun all ({1}) or only failed ({2}) tests, view passed tests ({3}), or enable the <a href="https://blog.jetbrains.com/webstorm/2018/10/testing-with-jest-in-webstorm/#run_tests_in_watch_mode">watch mode</a> to automatically rerun tests on changes. \nYou can also quickly find a specific test in {4}. Let\u2019s try it now: place the caret anywhere in the {4} area, type {5}, and press {6} to jump to our test.
-js.testing.jest.double.click=That\u2019s it! Use this feature whenever you need to quickly find your way through a lot of tests. Let\u2019s now double-click {0} that we\u2019ve found.
-js.testing.jest.fix.test=By double-clicking a test in {0}, we\u2019ve jumped straight to its location in the code. If you now hover over {1}, you\u2019ll see a popup explaining why the test failed. From there, you can also debug a test if needed. \nLet\u2019s now replace the incorrect value used for {2}: on line 6, replace {3} with {4}.
-js.testing.jest.re.run.test=Now that we have the right value for the expected result, we can rerun our test. Let\u2019s do it in a different way this time. See the {0} icon on the left of the test in the editor? This icon not only shows you the test status for the tests you\u2019ve run recently, but also lets you quickly run and debug a specific test.\n Let\u2019s click it and select {1}.
-js.testing.jest.success.run.coverage=Great job! Our test has successfully passed. \nLet\u2019s take a look at another handy tool. Click the {0} icon located next to the run/debug configurations menu.
-js.testing.jest.coverage.result=This is how you can quickly build a code coverage report showing how many files were covered with tests, including the percentage of lines that were covered in those files. Now let\u2019s close the coverage report with {0}.
-js.testing.jest.end=Congratulations! You\u2019ve made it to the end of this module. Most of what we\u2019ve learned also applies to the other test runners that {0} supports (except for code coverage and the watch mode). For more tips and tricks about testing apps with Jest, please take a look at <a href="https://blog.jetbrains.com/webstorm/2018/10/testing-with-jest-in-webstorm/">this</a> blog post. If you use other test runners, you may want to explore our <a href="https://www.jetbrains.com/help/webstorm/unit-testing-javascript.html">web help</a>.
+js.testing.jest.navigate=Now we can see the {0} tool window with the test results and a stack trace for the failed tests coming from a \
+ test runner in it. Apart from simply tracking the test progress, you can do a lot of other things here. You can rerun all ({1}) or only \
+ failed ({2}) tests, view passed tests ({3}), or enable the <a href="{4}">watch mode</a> to automatically rerun tests on changes.\n\
+ You can also quickly find a specific test in {5}. Let\u2019s try it now: place the caret anywhere in the {5} area, type {6}, and press {7} \
+ to jump to our test.
+js.testing.jest.double.click=That\u2019s it! Use this feature whenever you need to quickly find your way through a lot of tests. \
+ Let\u2019s now double-click {0} that we\u2019ve found.
+js.testing.jest.fix.test=By double-clicking a test in {0}, we\u2019ve jumped straight to its location in the code. If you now hover over {1}, \
+ you\u2019ll see a popup explaining why the test failed. From there, you can also debug a test if needed.\n\
+ Let\u2019s now replace the incorrect value used for {2}: on line 6, replace {3} with {4}.
+js.testing.jest.re.run.test=Now that we have the right value for the expected result, we can rerun our test. Let\u2019s do it in a different \
+ way this time. See the {0} icon on the left of the test in the editor? This icon not only shows you the test status for the tests you\u2019ve \
+ run recently, but also lets you quickly run and debug a specific test.\nLet\u2019s click it and select {1}.
+js.testing.jest.success.run.coverage=Great job! Our test has successfully passed.\nLet\u2019s take a look at another handy tool. \
+ Click the {0} icon located next to the run/debug configurations menu.
+js.testing.jest.coverage.result=This is how you can quickly build a code coverage report showing how many files were covered with tests, \
+ including the percentage of lines that were covered in those files. Now let\u2019s close the coverage report with {0}.
+js.testing.jest.end=Congratulations! You\u2019ve made it to the end of this module. Most of what we\u2019ve learned also applies to the other test \
+ runners that <ide/> supports (except for code coverage and the watch mode). For more tips and tricks about testing apps with Jest, please \
+ take a look at <a href="{0}">this</a> blog post. If you use other test runners, you may want to explore our <a href="{1}">web help</a>.
projects / idea / contrib.git / commitdiff