{"id":24258,"date":"2012-04-17T06:49:44","date_gmt":"2012-04-17T11:49:44","guid":{"rendered":"https:\/\/blogs.jetbrains.com\/idea\/?p=7179"},"modified":"2012-04-17T06:49:44","modified_gmt":"2012-04-17T11:49:44","slug":"code-coverage-for-javascript-unit-testing","status":"publish","type":"idea","link":"https:\/\/blog.jetbrains.com\/fr\/idea\/2012\/04\/code-coverage-for-javascript-unit-testing","title":{"rendered":"Code Coverage for JavaScript Unit Testing"},"content":{"rendered":"

This is a cross-post from WebStorm & PhpStorm blog<\/a>, originally posted by Sergey Simonchik.<\/em><\/p>\n

Measuring JavaScript code coverage naturally complements unit testing. It provides a clear picture of which parts of your code remain untested, and helps you focus additional tests on the uncovered code.<\/p>\n

From now on, users of JsTestDriver<\/a> can measure code coverage visually, right in the editor with JsTestDriver plugin for IntelliJ IDEA. Make sure you have installed 11.1.2 EAP<\/a> with the latest version of the plugin<\/a>.<\/p>\n

To illustrate the case, we have created a sample project<\/a> for you.<\/p>\n

When you open percentage-test.js<\/em> for the first time, you will see error highlighting on the TestCase<\/code> method call expression. Position the caret on the error-highlighted code, press Alt+Enter<\/i>\/Option+Enter<\/i> and choose “Add JsTestDriver assertion framework support” from the list of available intention actions.<\/p>\n

\"\"<\/p>\n

A global JavaScript library named \u201cJsTestDriver Assertion Framework\u201d will be created\u00a0and associated with a project. To view it, open the Settings dialog (File | Settings<\/i> or IntelliJ IDEA | Preferences<\/i>) and select JavaScript Libraries<\/i>.<\/p>\n

Before you can run any of your tests, you need to start the test server and capture at least one slave browser. The server does not have to reside on the machine where the test runner is located; similarly, the browsers themselves may be located on different machines.<\/p>\n

Starting JsTestDriver server locally<\/h3>\n

To launch the JsTestDriver server, look for the tool window at the bottom of the screen.<\/p>\n

\"\"<\/p>\n

Click the green arrow to the left of the address bar to start a local server. The status bar turns yellow to let you know the server is running, but has no slave browsers.<\/p>\n

\"\"<\/p>\n

Click the browser icon you want to capture. Alternatively, you can copy\u00a0the capture URL and paste it in a browser. The status bar turns green, and the corresponding browser icon lights up. Now you\u2019re ready to run tests.<\/p>\n

\"\"<\/p>\n

Running tests with code coverage<\/h3>\n

To run tests, right-click percentage.jstd<\/em> and choose Run ‘percentage.jstd’ with Coverage<\/i>. Tests will be run\u00a0against the local JsTestDriver server and you will get\u00a0a tree diagram.<\/p>\n

\"\"<\/p>\n

It also shows which lines were exercised by your unittests, and which weren’t, in two places. First, in your source files, it adds a green bar (exercised) or red bar (omitted) to the left of the source lines:<\/p>\n

\"\"<\/p>\n

You can also see test coverage statistics by file and by directory in your Project View:<\/p>\n

\"\"<\/p>\n

Excluding files from code coverage<\/h3>\n

If you use a JavaScript library in your code (e.g. jQuery), you don’t need to measure code coverage for library code. To exclude a JavaScript file from the coverage, open JsTestDriver Run Configuration you intend to run, select the Coverage<\/i> tab, and add the file to the excluded file paths.<\/p>\n

\"\"<\/a><\/p>\n

We’d appeciate to hear responses from you in our\u00a0issue tracker<\/a> ;).<\/p>\n

Test with pleasure!<\/em><\/p>\n","protected":false},"author":63,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","categories":[808],"tags":[197,207],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/idea\/24258"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/idea"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/types\/idea"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/users\/63"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/comments?post=24258"}],"version-history":[{"count":0,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/idea\/24258\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/media?parent=24258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/categories?post=24258"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/tags?post=24258"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/cross-post-tag?post=24258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}