johnbender / grunt-junit Goto Github PK

Just tested the plugin with jQuery UI. It gets stuck at the first test in the qunit task:

~/dev/jquery-ui [git:master+] $ JUNIT_OUTPUT=build/test-results/ grunt junit
Running "junit:env" task

Running "qunit:files" (qunit) task
Testing accordion.html

First time I ran it, the output dir didn't exist yet, but that's not the issue. After creating it, the result is still the same.

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

Both attributes provide the drill down information in the jenkins test results pages. Currently they aren't playing very nice:

http://swarm.jquery.org:8080/job/jQuery%20Mobile%20Phantom%20Master/120/testReport/

While the junit:env task checks if JUNIT_OUTPUT is set, the qunit task is overriden, so as long as the plugin is included and the qunit task in use, it'll still write files.

Instead there should be a check in tasks/qunit/phantom.js to not write any xml files if JUNIT_OUTPUT isn't set.

I can send a PR if you agree with this.