It allows you to enjoy all the benefits of JsTestDriver<\/a> right from the comfort of your IDE. This includes the following features:<\/p>\n The best way to understand how this works is to see it in action.<\/p>\n If you aren’t aware of JsTestDriver concepts, consider visiting http:\/\/code.google.com\/p\/js-test-driver\/wiki\/GettingStarted<\/a>. There is also an excellent tutorial introduction<\/a> to JavaScript unit testing by Christian Johansen.<\/p>\n We have created a sample project for you. Please download greeter-sample.zip<\/a>, extract it and open the project in your IDE.<\/p>\n If you open GreeterTest.js<\/em> for the first time, you will see error highlighting on the TestCase<\/span> method call expression. Position the caret on the error-highlighted code, press Alt+Enter<\/strong>\/Option+Enter<\/strong> and choose “Add JsTestDriver assertion framework support” from the list of available intention actions.<\/p>\n A global JavaScript library named “JsTestDriver Assertion Framework” will be created and associated with a project. To view it, open the Settings dialog (File | Settings<\/strong> or IntelliJ IDEA | Preferences<\/strong>) and select JavaScript Libraries<\/strong>.<\/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, and the browsers themselves can be on different machines as well.<\/p>\n To launch the JsTestDriver server, look for the tool window at the bottom of the screen.<\/p>\n Click the green arrow to the right of the address bar to start the server. The status bar turns yellow to let you know the server is running, but has no slave browsers.<\/p>\n Then, copy the capture URL and paste it in a browser. The status bar turns green, and the corresponding browser icon lights up. Now you’re ready to run tests.<\/p>\n To run tests, right-click greeter.jstd<\/em> and choose Run “greeter.jstd”<\/strong>. Tests will be run against the local JsTestDriver server.<\/p>\n In our case we have one failed test ‘GreeterTest.test greet null’. You can easily navigate from the stack trace to the source code that causes problems. You can also navigate from the test results tree to the test case\/test function declaration using the F4<\/strong> key.<\/p>\n In order to remove duplicated code that sets the greeter<\/span> local variable, you can refactor the Greeter object creation to a special method called setUp<\/span>, which is called before each test function is executed. Just invoke the Generate<\/em> action by pressing Alt+Insert<\/strong> inside of a TestCase<\/span> method call expression, and then choose “JsTestDriver Setup”.<\/p>\n Use the Shift+F10<\/strong> keyboard shortcut to re-run the tests after changing code.<\/p>\n Test with pleasure!<\/p>\n Download WebStorm for your platform from project EAP page<\/a>.<\/p>\n\n
\n
Getting started<\/h2>\n
Setup project<\/h3>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2011\/10\/webide-initial-project-state.png\")
<\/p>\nStarting JsTestDriver server locally<\/h3>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2011\/10\/webide-server-state-not-running.png\")
<\/p>\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2011\/10\/webide-server-state-no-captured-browsers.png\")
<\/p>\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2011\/10\/webide-server-state-ready.png\")
<\/p>\nRunning tests<\/span><\/h3>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2011\/10\/webide-tests-run-results.png\")
<\/p>\nGenerate code<\/h3>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2011\/10\/webide-setup-method-generate-action.png\")
<\/p>\n