WARNING - WARNING - WARNING
When I wrote this the intention was to release an example of integration between PhantomJS, Maven and Jasmine. I had no desire to maintain another project, and I find it surprising how many refer to this as one.
Use this as inspiration, and then take off your way. I have closed the Issue Tracker.
P.S.: Yes, I should have probably released this as a Gist instead...
PhantomJS - Jasmine XML - Example Project Layout
It is designed to be used standalone or within Maven.
Should work properly with PhantomJS version
$ phantomjs test/phantomjs_jasminexml_runner.js test/test_runner.html xml_output_dir/
This will produce a set of XML outputs, one for every Jasmine Test Suite.
Use within Maven
The project already provides a
pom.xml that does the trick. So a simple:
$ mvn test
$ mvn clean install
will launch the tests and, if they all pass, make the mvn build pass. If any test fails, the mvn build fails.
The new context has the following characteristics:
- isolated - the page doesn't know anything about phantom and phantom API
- controllable - the main phantom context provides API to control/influence the page context
So, how does it work?
The magic is done by 2 scripts:
jasmine.phantomjs-reporter.js is a plugin for Jasmine that saves the result of the
tests at the bottom of the webpage where the test runs.
phantomjs_jasminexml_runner.js instead runs the show, launches the tests,
extracts the result from the page, then saves it to the directory passed (see source).
Happy Testing ;-)
Licensing: Public Domain
The code of this project is relased under Public Domain and as such you are not required to do anything but use and enjoy it.
If, out of good will, want to put somewhere in your work a reference to this project as "inspiration", please feel free. But don't feel any obligation to do so.