automatically detect testing framework used and add required files

[kkozmic]

Ideal solution would be to have a single nuget package and to detect if the project we're being installed into uses NUnit or xUnit and add files appropriate for the given framework

Also we should do the same for any other framework/library we chose to support out of the box (like Windsor)

On top of that we should have a set of powershell commands for on demand tools/frameworks, something like:

ct-add windsor (add convention test files for Windsor)

[kkozmic]

I think there are three parts to this story (we can split them out into separate stories):

1. Figuring out how we can detect the testing framework we're using from within our Nuget package/test and doing the appropriate set up for that framework. This should support scenarios where multiple test frameworks are using inside a test project (it's not uncommon to have stated with NUnit and then move newer tests to xunit for example
2. Configuring additional frameworks we want to support conventions for OOTB (like Windsor)
3. having a Powershell command-line API to provide further options, like generating tests for conventions or something similar. This is probably of somewhat lower priority/v3_or_later feature

[JakeGinnivan]

I think this issue is obsolete, maybe in v3 we could do some real value adding with test framework integration, but lets drop this for now

[kkozmic]

fair enough. I'd love to have some powershell magic going on, but this may be our major v3 feature, I agree.

Let's stay focused for v2 on having nice clean API for common usage scenarios