I don't remember where I first read about it but I remember that I was happy to read that Visual Studio 2012 comes with a new Test Explorer. What's really cool about it is that it's no longer limited to just MsTest tests, but can run NUnit, xUnit ... you name it.
This means that my SpecFlow tests can be run from the new Test Explorer as well. You know, all SpecFlow actually does is translating the Gherkin lines you write into unit tests of your framework of choice. It should just work.
So they said...
Imagine my disappointment when the test explorer just reported "No unit tests found in solution" over and over again.
So after awhile I picked up that you (of course!) need to install adapters for the unit test frameworks you want to have the Test explorer to pick up.
That's quite easy. You go to Tools -> Extensions and Updates and search the Visual Studio Gallery (you'll find it under the Online-tab in the dialog) for NUnit, xUnit or whatever framework your using. What you are looking for are Test adapters for Visual Studio 2012. Like these:
When that is installed I was again happy to see that Visual Studio picks up my SpecFlow specifications and I can run them from the test explorer.
But wait, there is more
When I started to use the Test Explorer I found a couple of nuggets in there too, for us SpecFlow-users:
- Double clicking a test takes you too... The specification and not the generated test. Thank you very much mr Hidden pragma (#line hidden)
- You can run only failed, or passed for that matter and even a shortcut for rerunning the last test run. It seems like TDD practices are getting a firm footing at Microsoft...
- There is, from the Test menu, an option to rerun the tests on every build. So it's a bit like a poor mans MightyMoose and NCrunch test runners.
These small things made me happy and my productivity boost a bit again. Once I knew who to get it to run with the testframeworks I normally use.
I like it!
If you liked this post ... here's more for you:
Published byon Last updated