Console runner?

Aug 10, 2012 at 8:44 AM

The recent discussion in the issue tracker has got me thinking - how about a console runner for NinjaTurtles? This would cover the following use cases:

1. Running all tests marked with [MutationTest] in an assembly.

2. Automatically running mutation tests for a specified class and method (or just class). In case of the class, specify something like a BindingFlags enum value to identify which methods.

An advantage is it gives us a single operation with which to scope the creation of an output file, unlike the current NUnit integrated mode, where each method's mutation tests must either create a new file or merge into an existing one - no easily identifiable start point to clear this down.

Also, this might sit better in a CI/automated build environment.

Thoughts anyone?

Sep 6, 2012 at 8:53 AM

I had meant to reply to this earlier.  Obviously a good idea, especially for experimentation.  I have at this point seen what you've done with the console runner, and it's an awsome job.  Keep em coming.