lineman spec-ci tends to hang on Windows, the tests run but wait over a minute before returning to the command line.
In xUnit CI reporting mode, a Jasmine test would fail with the parameters in the message attribute containing double quotes. These were not escaped in the output XML file, and that broke the Jenkins parser, failing the build.
The breaking version:
<testcase name="PhantomJS 1.9 ..."><failure name="..."
message="TypeError: 'undefined' is not an object
(evaluating 'spyOn(http, "post").and.callThrough')"
<testcase name="PhantomJS 1.9 .."><failure name="..."
message="TypeError: 'undefined' is not an object
(evaluating 'spyOn(http, "post").and.callThrough')"
This has been tested locally on Centos 6.5 and on Windows 7 by updating the version in the node_modules/lineman/package.json and running npm install from there, and seems to work, fixing both issues. It has not been tested with an official Lineman build.
We have two problems
lineman spec-ci
tends to hang on Windows, the tests run but wait over a minute before returning to the command line.The breaking version:
I replaced testem with the current 0.7.6 and this fixes https://github.com/airportyh/testem/issues/511 (as of 0.7.2) and the new xunit output is:
This has been tested locally on Centos 6.5 and on Windows 7 by updating the version in the
node_modules/lineman/package.json
and runningnpm install
from there, and seems to work, fixing both issues. It has not been tested with an official Lineman build.