search

nikgoodley-ibboost / phantomjs-qunit-runner

Automatically exported from code.google.com/p/phantomjs-qunit-runner
0 stars 0 forks source link

Make the test output JUnit xml compliant (currently untested) #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 

Make the test output JUnit xml compliant (currently untested)

Original issue reported on code.google.com by spazkus@kennychua.net on 14 Dec 2011 at 11:11

GoogleCodeExporter commented 8 years ago 
I'm working on a fix to the javascript wrapper to output the xml correctly.  
Right now, it just shows that there is an error.  I'm re-arranging the calls 
and using the qunit.log method to get the actual, expected, and message instead 
of just dumping out that there was an error.  I should have this soon (if you 
want it).

Original comment by br...@newtonius.com on 28 May 2012 at 12:40

GoogleCodeExporter commented 8 years ago 
I have a runner javascript that will output junit compliant xml.  I would like 
to submit it to this project if you guys are still working on it.  I've 
attached the runner.

It will also handle all of the weird module cases, whether or not modules are 
started or not.

Attached files are:
foo.js - source script
fooTest.js - test script
phantomjs-qunit-runner.js - my version of the test runner
fooResults.xml - example results

Original comment by br...@newtonius.com on 28 May 2012 at 9:31

Attachments:

GoogleCodeExporter commented 8 years ago 
Deleted the last runner javacript, I've added some handling for xml special 
characters so that <, >, and & inside of messages won't blow up the xml.

Original comment by br...@newtonius.com on 28 May 2012 at 9:40

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi Brian, that's fantastic, thanks for sharing! I'll update it shortly when I 
get the chance

Original comment by spazkus@kennychua.net on 28 May 2012 at 11:56