Our team recently upgraded to Grunt 0.4.0 and Phantom JS 1.9.0 and faced reliability issues with the new Grunt-QUnit plugin. We decided to find an alternative way to run our tests.
Visu Patlolla found QUnit’s Phantom JS add-on worked very well with our new set up. However, it did not generate a JUnit report. See https://github.com/jquery/qunit/tree/master/addons/phantomjs
In order to meet our requirements, I moved the JUnit report generation feature from Phantom JS QUnit Runner to QUnit’s Phantom JS add-on. I forked the QUnit repo https://github.com/leedavidr/qunit/tree/master/addons/phantomjs with these changes. This version hardcodes the location of the JUnit reports, but it can easily be modified to take in a system property or parameter.