- Lack of support for internal classes, that was supported in the original VS functionality (along with setting the internalsvisibleto() attribute)
- The unit test created required renaming.
I know creating a true unit test generator is impossible... you should be creating the unit test first. But it would be nice if the code exist, creating tests based on symbols, known patterns, ect. Support for WF unit testing would be nice as well.
Very useful extension not only adding back functionality which had been removed but also extending the functionality by adding in support for different testing frameworks. The biggest problem however is that it doesn't support generating tests for internal classes and methods. It should be rather trivial for this to be fixed and an InternalsVisibileTo attribue added to AssemblyInfo. Once that's been done then I'll give it 5 stars.
Finally something to replace the functionality that was removed from VS. It does exactly what I need it to do. I installed it through VS's "Extensions and Updates" wizard and had no problems. IMHO it works better than what was taken out of VS.
Thanks Guys for providing this functionality through an extension. I'll use it a lot.
This simple tool makes adding unit tests for my classes a breeze. Especially when I am implementing a interface. Just create my class, implement the interface classes. Right click and generate all my tests.. then start knocking out my methods one by one good old TDD style. I love it. Great tool. I would how ever like to see something like Netbeans and IntelliJ to when generating tests in that they make a instance, a actual, and a expected variable for me. Granted it's not always right, but it's nice to have the majority of that put in. Just a thought.
Does exactly what it promises, setting up the plumbing and creating one test method, or a test method for EVERY public methods of a public class. Obviously not the same as the discontinued feature, but then it states that clearly. It obviously assumes that you have reviewed the blog posts and documentation listed with the extension.
Erm doesnt work at least on Express 2013.. 1 hr of trying.
Cant even upload image of pop-up error.
30/04/2014 20:27:24 - Searching for applicable products... 30/04/2014 20:27:24 - Found installed product - Microsoft Visual Studio 2010 Premium 30/04/2014 20:27:24 - Found installed product - Microsoft Visual Studio Express 2013 for Web 30/04/2014 20:27:24 - Found installed product - Global Location 30/04/2014 20:27:24 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products. at VSIXInstaller.App.InitializeInstall() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute()
People who ever developed this plugin ,please don't call yourself a programmer. This is a useless tool that does nothing . Its a shame on MS , that they can't get a back cool feature that is needed by its developer community , even after two releases of visual studio.
I unfortunatly activate the "not show me again" (or something like that...) on the parameter box who pops when you do a right-click -> generate unit test. Someone knows how to re-activate it ?
If you try to generate a unit test for a project targeting 4.5.1 where no unit test project currently exists, the generated test project targets 4.5 and is therefore unable to reference the code being tested. I have to change the target framework manually. It would be good if the target framework were copied from the source project.
As it doesn't look like the authors are posting here at the moment, a workaround for the project target framework version is to modify the default Visual Studio project template for unit tests. This is located at C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ProhectTemplates\CSharp\Test\1033\UnitTestProject\UnitTestProject.csprj (you may need to change 1033 to be your language code).
Originally this file contains:
You can change it to target your framework version, but be aware that any project created manually will now have this version too:
Hi, I have downloaded the extension, my VS is 2012 update 4, opened my project when positioning cursor on a method, right click, I do not see the generate unit test item in the menu.
I changed the method to public, still can not see the item. I checked the nugget manager, it is right there in the installed packages
Thanks for your help
I have the same problem. "Generate Unit Test" does not show up in menu. I have VS 2012 update 3. I just installed the latest Unit Test Generator, 18.104.22.1680. I created a new console project and tried right clicking inside the the programs's "Main" function -- no Generate option. I tried creating another public method -- again no option. I tried first creating a test project for this project - still no option. I tried, as someone suggested, building the project first -- still nothing. I tried many other things - no option.
People have been asking this same question in this forum since July. NO-ONE has responded with any possible help.
I think I found the answer. I tried various project types: Console, Forms, WCF, Class library. The option finally showed up in a Class Library. When I was searching for more articles, I also found this: http://blogs.msdn.com/b/willy-peter_schaub/archive/2013/07/19/exploring-the-unit-test-generator-vs-extension-v1-rc.aspx
His instructions start by telling us to create a Class Library. However neither the release notes nor the Quick Reference Unit Test Generator Overview had mentioned that it only works for a Class Library.
I have upgraded extension for few times and every time I upgrade I loose "connection" to my output projects in solution. So I can't pick from my existing unit test projects but I have to create a new one and then move the generated file to proper project.
Did anyone has this issue or any kind of workarounds ?
I don't find this tool that useful if it doesn't autofill the params for the method it is testing. Also, it should make assumptions on what you will asset. If the method returns a bool assert that the response should be true. If it should be false that is a small change the developer can make.
This is a small step up from copying and pasting an existing test method and renaming it. Please consider adding the auto-gen that 2010 had. At minimum for VSTest.
Add me to the increasingly massive list of people to ignore who are asking to test non-public methods. It would be nice to not have to find-replace everything with "public" just to work around your dogma.
Seriously, at least provide a reason for this.