Run js tests, for example jasmine
I know I'll be disappointing many people by saying this, but at the moment I don't see this happening for NCrunch in future.
Contrary to what some believe, properly adding JS support to NCrunch is an enormous task. It would involve a complete reconstruction of all build and runtime components of NCrunch. It would also require integration with a huge range of different frameworks and toolsets, many of which are in a constant state of flux. The JS eco-system is much larger and more fragmented than .NET, with so many different ways of approaching even the simplest of scenarios.
Supporting JS through its never-ending evolution would massively increase the effort required to keep NCrunch up to date - such that new development on features would essentially stop, with all effort going into maintaining integration points.
It's been suggested that there is the possibility for a half-way approach, such as implementing only Jasmine/QUnit support, or not tracking code coverage, etc. I don't feel this is a solution, as even the smallest step into JS will set eventual expectations on full support, and there is still a potential infinite number of unconsidered edge cases that will give people unending frustration. I refuse to implement a feature like this unless I know I can do it properly and to a standard worthy of the product.
Artem Govorov's WallabyJS has been gathering momentum lately and looks like a really good option for continuous/concurrent testing in the JS space. This project was inspired by NCrunch, and is likewise run by a passionate developer who greatly cares for his product. Its price is very reasonable and I recommend taking a look - http://wallabyjs.com/
Brett Jacobson commented
I have been using http://wallabyjs.com/ to run my jasmine tests for a while now, happy so far.
Seb Smith commented
harry patel commented
Magnus Lidbom commented
Code here: https://github.com/DanTup/TestAdapters
I would love it if you could do this classic lean. We don't have to have full and perfect integration for it to be quite useful. Just getting the results into the same result list as .net tests would be good enough to release the first version in my opinion.
Magnus Lidbom commented
Just chiming in to say that this can probably be far easier than you think.
You really would NOT need to implement your own runner to do it.
I absolutely would not expect grid support out of something like this. At least not for a good long time.