Comment 3 for bug 538070

Hi, hope you don't mind that I jump in on this one,

We're also running into the same problem; our current work-around is to run all QUnit tests within a single NUnit test. The advantage of running QUnit tests in a source is to be able to translate 1:1 to NUnit tests so that our build system reports QUnit test failures individually rather than in summary, and that our test counts include both NUnit and QUnit tests. Naturally, running browser-based tests is quite time-consuming in the normal flow of development, and since we don't want our back-end developers to be waiting for the full suite of javascript tests when working in another area of the system, we prefer to defer running of these until the build on the build server (hence Explicit+Category); UI devs run the JS tests more regularily, but manually.

Stein Jakob