We are pleased to announce that the v1.3 of the Unit Test Generator has shipped. It is a bug-fix revision and does not introduce new features.
why bug fix?
This bug fix release addresses and resolves an elusive gremlin: Bug 9814: Unit test generator breaks nuget [vsarguidance: 20485] and finally brings us to a zero (0) bug count.
Fix: We no longer include NuGet assemblies in the vsix.
so, what’s the intent and plans for this extension?
We often get the question as to why the unit test generation feature was removed from the product and why this extension does not replicate the features from the previous product feature. Let’s try to find some answers.
There was a change in architecture to support multiple unit testing frameworks, and with Visual Studio 2012 and 2013 we got support for third party unit testing frameworks. See http://msdn.microsoft.com/en-us/library/hh704261(v=vs.110).aspx#whatsnewtestingunittests for more information. Using the Unit test Generator extension you can now generate NUnit and XUnit unit tests as well as MSTest unit tests.
There is no debate that the Rangers extension is simpler than the original feature, but arguably supports the most useful functionality. In Unit Test Generator under the bonnet (hood) … aka vsarUnitTestFx we were very transparent with our project principles and vision, highlighting that we are not resurrecting the old command or its features.
Will there be a v2? It depends what we hear from the ALM community (you). We need to ensure a need, business value and alignment with the product group plans for the product.
- Release Notes
- Unit Test Generator Overview
- Peruse Exploring the Unit Test Generator VS Extension v1.RC and Unit Test Generator v1.2 and Tim’s Gremlins for a quick feature and usage overview of the configuration options and code generation features within the methods and classes.
We can’t wait to hear from you, learn more about your experience using the extension and hear your thoughts on “what next”.
Here are some ways to connect with us: