PhantomJS  page     

PhantomJS is a headless WebKit. FuncUnit integrates with Phantom to run tests from the commandline. This has large performance benefits, enough that it makes it much more feasible to integrate FuncUnit tests into your build process without significantly slowing it down.

Install

Before you can use PhantomJS, you have to install it. The other automation tools come prepackaged in JMVC, but Phantom is too large of a download.

On Mac

1. Download PhantomJS
2. Unzip it somewhere like: /Applications/
3. Add it to your path:

sudo ln -s /Applications/phantomjs-1.3.0/bin/phantomjs /usr/local/bin/

Note: Not all systems will have /usr/local/bin/. Some systems will have: /usr/bin/, /bin/, or usr/X11/bin instead.

On Windows

1. Download PhantomJS
2. Install it
3. Add it to your path. For information on setting path variable in Windows, click here.

Use

To run any test via PhantomJS, use funcunit/run

./js funcunit/run phantomjs path/to/funcunit.html

Debugging

If you notice a broken test, debugging it in Phantom is not the place to start. Open the test in browser, and verify the same test breaks there. If so, debug the test in browser.

If you notice the more rare event that a test breaks in Phantom but works in browser, you can use console.log to debug it. In funcunit/commandline/phantomjs.js, uncomment the print: true option. Add console.logs to your code and debug.

One thing to be aware of is that phantomjs tests run within an iframe in the funcunit.html page. This is different from the normal behavior of opening the application page using window.open. Phantom doesn't support window.open, so a frame is used instead. This can occassionally cause problems if your application assumes it is running within window.top.