dlmcdonald / unittestgenerator

Visual studio for Mac extension to generate unit tests from a method

UnitTestGenerator for Visual Studio for Mac

Visual studio for Mac extension to generate NUnit unit tests from any method

About

This extension was created to facilitate the creation of unit tests (Currently in the context of Xamarin.Forms). Currently, this extension only supports generation of NUnit tests and uses Moq to create mock items.

Installation

• Download the latest mpack file from the Releases page
• Open Extensions from the Visual Studio Menu
• Click install from file
• Browse to the downloaded file
• Restart your Visual Studio for Mac

Usage

• Right click on a method and hit "Generate Unit Test" at the bottom of the Context Menu
  • If the method is private, this option will be disabled
  • If you have not used this extension before in this project, it will prompt you to select your UnitTest project. It will then generate a Solution folder and add a json config file
• A UnitTest class will be generated with the format <MethodName>Should.cs
  • A default SetUp method will also be generated
• A dialog will appear, prompting you to supply the test name
• Once you confirm the test name, the unit test method will be generated
• The following items will be generated, based on the signature of the method:
  • expected variable based on the return type of the method (if applicable)
  • a variable for each parameter of the method with a default value based on the type of the parameter
  • Mock objects for all constructor parameters
  • Constructor initialization
  • result variable assigned to the method call
  • A default assert
  • All the using statements based on the classes used in your method and constructor

unittestgenerator's Issues

Non-interface types need to be instantiated instead of mocked

When generating a unit test that has a non-interface type in the constructor will generate code that is incorrect.

For example:

public class TestClass
{
    public TestClass(int foo)
    {
    }
}

When creating the test for this, the following will be generated:

var foo = new Mock<int>();
var vm = new TestClass(foo.Object);

this code will not compile.
We should rather use Mocks for interface types and instantiate the concrete types:

var foo = default(int);
var vm = new TestClass(foo);

Default Setup method as empty method to remove unnecessary dependencies

The default setup method currently includes Xamarin.MockForms.Init.

Remove the lines from the default setup method

Also, remove the unnecessary setting to use custom setup method and make the plugin check if there are any lines in the custom setup lines

Add custom "SetUp" for test

Add the ability to define a custom "SetUp" Method in the configuration file to override the default

Automatically resolve namespaces for items in the generated test method

Currently, after creating the test method, there is a manual process of resolving all the imports. I would like to see if I can import all the required namespaces automatically

Update methods to allow for async/await

Use the async version the methods so that progress can be show and we don't have to ConfigureAwait for everything

Add error handling

Add error handling to project

• User errors to be handled with an error dialog
• Informational errors to be displayed to a VS log

Convert helper classes to services to allow them to be used with CompositionManager.GetExportedValue

• Add interfaces for helper classes
• Update naming convention of helper classes
• Update references of helper classes to be instantiated by CompositionManager.GetExportedValue