search

sbrandwoo / grunt-qunit-junit

JUnit compatible XML reporter for QUnit and grunt 0.4
MIT License
16 stars 5 forks source link

Grunt 0.4 Release #4

Closed tkellen closed 10 years ago

tkellen commented 11 years ago

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!

sbrandwoo commented 11 years ago

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?

Do you think that this plugin, which provides a reporting tool for QUnit, is best placed as a separate plugin, or as part of grunt-contrib-qunit?

I have had some difficultly in getting changes to grunt-contrib-qunit approved, so I'm not yet convinced by the structure of the contrib projects.

tkellen commented 11 years ago

ping @cowboy

cowboy commented 11 years ago

Custom reporter support seems like it could be useful in the core task. Is it possible for the code that outputs the XML to work with other, similar plugins?

sbrandwoo commented 11 years ago

The event based system of Grunt 0.4 does much of the abstraction already but there is one big step that is done before any XML generation happens, which could possibly be shared to other reporting plugins.

This big step is to capture all of the individual events and build up a summary object of everything that happened. XML is then built from this summary, rather than from each individual event on the fly. The rationale behind this is that we often see test runners that fail to finish, or that timeout, or that are missing modules and the event order doesn't necessarily match the XML write order - so it's clearer to do all the XML generation at the end.

I imagine this style of summary object could become another event of grunt-contrib-qunit, reducing grunt-qunit-junit to some simple loops and XML writing.