Pratap Lakshman [MSFT] commented
-1 don't re-invent the wheel, point people at one of the many libraries in the node eco-system that does this already. Maybe allow more integration.
Brandon Wittwer commented
A native JS test runner with debugging in both VS and TFS build environments are definitely needed. JS Tests should be first class citizens. The only configuration to consider is how to uniquely identify the test syntax, boundaries, and assertion methods. So OOTB, jasmine, QUnit, Mocha... but then a published standard to tell developers how to configure the test runner to be able to accept ANY framework.
Richard Hepburn commented
The test runner should also support TypeScript and should support attaching to the browser process so you can debug into the tests from inside of VS. Currently, it's very difficult to provide a productive development experience that allows developers to debug into their Unit Tests (QUnit, Jasmine, etc...) from within the VS IDE. The only way to do this now, is to create a separate test runner page (e.g. testrunner.html) and set that as your start page and then run VS. Most other test runner tools like Chutzpah and Karma don't allow you to debug the tests from within VS. It's also important to be able to integrate the test results back into VS so all test results are in one place.
I should see not just a test runner, but the the runner should be capable of debug tests too.
Hugo Biarge commented
It would be nice to include code converge capabilities and integrarte the test and coverage results with Visual Studio and Team Foundation Server - Visual Studio. Online.