phantomjs, Jasmine, and CI

[gmusick]

Great tool! I wanted to use it to run my Jasmine tests headless as a part of my CI, which, for reporting purposes, needs results written to a file in an XML format. I made some updates that allow for file writing and also loading up a local file using relative paths rather than using the file:/// notation. I edited the run-jasmine.js example to use these features. run-jasmine.js now exposes a window.fileWriter object which can be used by a custom Jasmine reporter to write results to disk (see https://github.com/gmusick/jasmine-reporters/blob/master/nunit-reporter.js for an example reporter that does this).

Thanks,

Greg

[ariya]

The file access is rather dangerous with proper sandboxing, see issue 41 (http://code.google.com/p/phantomjs/issues/detail?id=41). Until the better security model is implement, this poses too much risk for the user.

As a workaround, the result can be written out to stdout using console.log and then redirected to a file (when invoking phantomjs).

I've been using practically the above approach for CI, it works rather well. To overcome the file:// scheme problem and use relative path instead, it is wrapped in a simple shell script which would invoke phantomjs + run-jasmine with the proper local file URL using file scheme.