I was a bit confused that the extenion is named Unitverse and this repo unittestgenerator.

Proposal: rename this repo. Github add a redirect (also for the git url), so the rename is safe - all old hyperlinks and clone urls will still work!

Of course you could add some tags if you think this repo is hard to find with the new name

With Generation Options -> "Emit using directives outside namespace" set to True, test classes are still generated with using statements inside namespace.

Seeing in 0.122.0.0 and after VS restarts.

In Version 0.105 it was possible to generate tests to a temporary directory - with version 0.107 it forces me to choose a project. So I always have to go there and delete the file afterwards.

The usage of temporary generated files helps a lot in some use cases

Hi again :)

Version: 0.104.0.0

My .unitTestGeneratorConfig has the following lines:

TestProjectNaming={0}.Test
TestFileNaming={0}Test
TestTypeNaming={0}Test

But in the settings window it shows the plural form:

And when I export, it will override these lines with Tests

When generating in VS2022 ->

Exception raised
System.MissingMethodException: Method not found: 'EnvDTE.Solution EnvDTE._DTE.get_Solution()'.

at Unitverse.Helper.ProjectItemModel.get_TargetProject()

at Unitverse.Commands.GenerateTestForSymbolCommand.<>c__DisplayClass13_0.b__0() in D:\a\unittestgenerator\unittestgenerator\src\Unitverse\Commands\GenerateTestForSymbolCommand.cs:line 214

at Unitverse.Helper.Attempt.Action(Action action, IUnitTestGeneratorPackage package) in D:\a\unittestgenerator\unittestgenerator\src\Unitverse\Helper\Attempt.cs:line 21

See https://developercommunity.visualstudio.com/t/dte-events-not-working-in-vs2022/1455126
Also see https://cezarypiatek.github.io/post/migrate-vsix-to-vs2022/

I'd like to suggest a new feature:
Adding an option to define the scope of the methods/etc. selected for test generation.

• public only
• public and internal
• [public, internal and private] <-- maybe

I believe, based on my use, that only public items are selected for test generation. I also know that not everyone believes that non-public methods, should be included in units tests.

Adding the feature doesn't limit these beliefs, but does open up the use of Unitverse extension to more user scenarios.

Thanks for your consideration.

When I click "Generate test for method 'SomeMethod'..." I want to select project to which the test will be added, like is in NUnit Visual Studio Test Generator.

Some methods I test in the project with unit tests, and some methods I test with higher correlations (e.g. with database connection), than project has a different name.

Also, our project names have evolved over the years, so we have many patterns. Some projects I could refactor, but not all.

Do you have any ideas for my case?

Set page titles and favicon for GitHub pages - ideally title should be

Unitverse | Page Title

But not Unitverse | Unitverse for the home page

Ideally we could add a favicon too

If there is a protected generic method and the generic type cannot be inferred (I.e. there are no parameters of one or more of the type parameters), then the type signature should be specified explicitly. Example found was on a public wrapper for a protected method.

We want to emit interface tests for IEquatable

This also needs to cover the case where T is not the type on which the interface is declared.

I.e. we need to support all of these:

SomeType : IEquatable<SomeType>
SomeType : IEquatable<SomeOtherType>
SomeType : IEquatable<SomeType>, IEquatable<SomeOtherType>

Currently you can only enter one pattern for project naming conventions (e.g. {0}.Tests).

It would be useful to support multiple patterns, so solutions without a strong naming convention can be supported.

Not sure if we're doing the testing for nullable reference types correctly - string? explicitly can be null, and we're omitting the null test in that case

If we're using FluentAssertions, then Assert.Fail should pass through to the underlying test framework type
Also, for xunit, rather than Assert.True(false) - it would be nicer to just throw new NotImplementedException

When right clicking a class symbol and selecting 'generate tests' it will complain if any tests exist and ask for regeneration to happen. It could be modified such that any new tests are added to the test class in a non-destructive way.

This could be the default behaviour for generate tests, or we could add a new command 'generate new tests only'.

Would be cool if this generator detects and supports Moq.AutoMock

e.g.

var mocker = new AutoMocker();
_logger = mocker.GetMock<ILogger<MyClass>>();
_sut = mocker.CreateInstance<MyClass>();

Hey, love the extension!

One thing I would like to see is an option to name variables without the leading underscore.

And another would for the testClass to be called sut (System Under Test)

Currently Type.GetType("TestValue41241") is emitted - we should emit typeof(string) instead

Hi

Often if my extension methods require some specific classes, I will just put them in the same file

However then when I try to generate the extension method tests, it tries to generate tests for those classes which I defined earlier in the same file

This one is a bigger one - but...

Given a class that takes a constructor dependency and stores it in a field _field - then whenever a method call or property get is made to _field within the context of the method - detect that call and automatically configure the mock with default values.

Would just save a bunch of typing.

Currently we emit a derived class when testing an abstract class. We may want to do that to allow protected methods to be tested - even if they are not part of an abstract class.

There isn't an example of a model class that just has simple value types for params with matching properties to demonstrate *IsInitializedCorrectly tests

Minor polish issue, would be great is this could be configurable

For new users, they may want to just select 'Generate temporary file' if they get the generation dialogue on first use. So adding an option to the UI for 'no target project' would be useful.

Right now we have good coverage on creation of new tests - but we don't have great coverage on generation of additional tests where a test class already exists. Need to think about how best to achieve this and cover all bases from a framework set point of view.

Sometimes when refactoring the test class file might be incorrectly named. If performance allows it, we should be able to navigate to the test type using the type name.

Probably worth explaining a few things in the code base

• How the tests are mostly driven from the test resources and then each test class is generated 18 times (one for each framework, with and without fluent assertions)
• How the general ethos is to care less about the output being really specific and more about producing something that compiles (within reason)
• How the example generator works, and how the build protection works
• Areas that could do with some tidying up
• General code map

Hi again :)

Input:

public delegate void ExpandConstantDelegate(string input, out string output);
public static void RegisterExpandConstantCallback(ExpandConstantDelegate callback)
{
}

Generated test

 [Test]
        public static void CanCallRegisterExpandConstantCallback()
        {
            // Arrange
            Exports.ExpandConstantDelegate callback = (x, y) => { };
                                                          ^ Should have out keyword   
            // Act
            Exports.RegisterExpandConstantCallback(callback);
            
            // Assert
            Assert.Fail("Create or modify test");
        }

Easy to manually fix, just thought I would report it

Maybe this is really opionated,

But the using in the default class template of Visual studio is above the namespace

Current result:

namespace MyNameSpace
{
    using System;
    using Xunit;
    using FluentAssertions;

    public class MyClassTests
    {

expected/desired:

using System;
using Xunit;
using FluentAssertions;

namespace MyNameSpace
{
    public class MyClassTests
    {

For example, the new class template in VS2022 generates:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace MyNameSpace
{
    internal class Class1
    {
    }
}

If we use Roslyn 4 in the core library, we could support things in C# 10 (file scoped namespaces being one).

The boilerplate generator does this by referencing an older version and using reflection. This might work but given that this extension emits code by building Roslyn trees it might make it tricky.

This could potentially lead to a version of Unitverse that could be compiled for VS2017.

If an input param type and return type are List, then the mapping method strategy can produce some odd results

Hi again :) Really enjoying this extension so far

I would like to see an option to disable the auto generated tests which check the behavior with null types. Our code base never has any nulls, so we also don't guard against them, and also are not interested in testing for them

Also an option to disable the CanConstruct test

Hello again :)

Very often I expose my internals to my tests, and test my internal classes. Currently this extension requires class to be public.

...or maybe something else. But the stylesheet on readthedocs is awful.

For Func, currently default(Func) is emitted. It would be better if () => T was emitted, and we use the assignment value helper to generate a value for T.

For Action, we should emit () => { }

For the parameters, we should emit:

0 parameters: ()
1 parameter: x
2/3 parameters: (x, y) or (x, y, z)
4+ parameters: (a, b, c, d), (a, b, c, d, e) etc

Very minor issue, this window doesn't respond to scroll wheel events

Example:

public abstract class Foo
{
    protected abstract bool TryMe(string bar, out string foobar);

    public void DoSomething()
    {
        // Magic
    }
}

When you generate tests for this, it will generated an implementation like below - note the "out" parameter modifier is missing:

public class TestFoo : Foo
{
    protected override bool TryMe(string bar, string foobar)
    {
        return default(bool);
    }
}

namespace MyNameSpace
{
    public record MyRecord
    {
        public string Method1()
        {
            return "Hai";
        }
    }
}

gives:

note: it works when MyRecord is a class

• VS2022 (17.1.0)
• Extension: 0.100.0.0
• .NET 5 class library

Hi, so now the extension can be configured, it works great.

However each team member would have to configure it to match the project style. It would be amazing if the config could be exported, so I could add it to the .git repository, and then anyone using the project would automatically get the same settings

I would like to see a .unitverse file which can be saved to the repository

Would be great if the comments for AAA are generated. (// Arrange, // Act, // Assert)

e.g.

// Arrange
var repository = Substitute.For<IClientRepository>();
var client = new Client(repository);

// Act
client.Save();

// Assert
mock.Received.SomeMethod();

Anytime I try to generate tests, whether it be at a project level, class level, or method level, I get this exception.

Microsoft Visual Studio

Unitverse

Exception raised
System.MissingMethodException: Method not found: 'EnvDTE.Solution EnvDTE._DTE.get_Solution()'.

at Unitverse.Helper.ProjectItemModel.get_TargetProject()

at Unitverse.Commands.GenerateUnitTestsCommand.<>c__DisplayClass12_0.b__0() in D:\a\unittestgenerator\unittestgenerator\src\Unitverse\Commands\GenerateUnitTestsCommand.cs:line 135

at Unitverse.Helper.Attempt.Action(Action action, IUnitTestGeneratorPackage package) in D:\a\unittestgenerator\unittestgenerator\src\Unitverse\Helper\Attempt.cs:line 21

OK

I am using VS2022 and the extension version is 0.67.0.0

A few things in the code need tidying up - some usings no longer required, some things could be extracted to constants (name of options files, extension GUID).

In Version 0.107.0 when disabling "Use Fluent Assertions" in the "Unitverse options for source project '' they are still being generated.

Given this test class

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading;
using FluentAssertions;
using Moq;
using Xunit;

namespace MyNameSpace
{
    using MyNameSpace.Domain; // Note!

    public class MyTests{ 

....

}

1. Enable directives outside namespace.
2. Generate a test methode for an existing class (and with exiting tests class)

Current result

1. Test will be added (nice!)
2. Almost all usings are removed! (not expected)

Result:

using MyNameSpace.Domain; 
// Missing usings

namespace MyNameSpace
{
        public class MyTests{ 

        [Fact]
        public void CanCall() {... }


}

Note:

• when missing using MyNameSpace.Domain; // Note!, we have as a result 0 usings
• this isn't an issue when directives outside is false

Environment: Visual Studio 2022 (Version 17.2.0 Preview 1.0)
Unitverse: 0.113.0.0

When I Click "Generate test for method ...", I get a MessageBox with the content:

Unitverse

Exception raised
System.NotImplementedException: Nie zaimplementowano. (Exception from HRESULT: 0x80004001 (E_NOTIMPL))

   at EnvDTE.Project.get_FileName()
   at Unitverse.Helper.VsProjectHelper.<FindProjects>d__5.MoveNext() in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\VsProjectHelper.cs:line 60
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at Unitverse.Helper.ProjectMappingFactory.CreateMappingFor(Project sourceProject, IUnitTestGeneratorOptions baseOptions, Boolean interactive, Boolean skipManuallySelectedTargetResolution) in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\ProjectMappingFactory.cs:line 26
   at Unitverse.Commands.GenerateTestForSymbolCommand.<>c__DisplayClass13_0.<Execute>b__0() in D:\a\Unitverse\Unitverse\src\Unitverse\Commands\GenerateTestForSymbolCommand.cs:line 205
   at Unitverse.Helper.Attempt.Action(Action action, IUnitTestGeneratorPackage package) in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\Attempt.cs:line 18

When I Click "Go to tests", I get a MessageBox with the content:

Unitverse

Exception raised
System.NotImplementedException: Nie zaimplementowano. (Exception from HRESULT: 0x80004001 (E_NOTIMPL))

   at EnvDTE.Project.get_FileName()
   at Unitverse.Helper.VsProjectHelper.<FindProjects>d__5.MoveNext() in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\VsProjectHelper.cs:line 60
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at Unitverse.Helper.ProjectMappingFactory.CreateMappingFor(Project sourceProject, IUnitTestGeneratorOptions baseOptions, Boolean interactive, Boolean skipManuallySelectedTargetResolution) in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\ProjectMappingFactory.cs:line 26
   at Unitverse.Helper.GoToTestsHelper.FindTestsFor(ProjectItemModel source, IUnitTestGeneratorPackage package) in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\GoToTestsHelper.cs:line 14
   at Unitverse.Commands.GoToUnitTestsForSymbolCommand.<Execute>b__8_0() in D:\a\Unitverse\Unitverse\src\Unitverse\Commands\GoToUnitTestsForSymbolCommand.cs:line 107
   at Unitverse.Helper.Attempt.Action(Action action, IUnitTestGeneratorPackage package) in D:\a\Unitverse\Unitverse\src\Unitverse\Helper\Attempt.cs:line 18

It would be interesting to have a 'statistics' function to track generated content

Number of lines of code generated
Number of test methods generated
Number of incomplete test methods generated (i.e. something with an Assert.Fail)
Number of complete test methods generated

If you

• have a test class with a protected property
• enable the option to emit a derived class to expose protected members (enabled by default)
• turn off strategies that test protected members

Then the test class will be emitted using the Abstract strategy, even though the derived class isn't necessary. This requires a two-pass evaluation of strategies. First pass 'marks' members that have strategies emitted for them. Abstract strategy would then be picked only if any protected members are marked.

The documentation doesn't mention generation for abstract classes, for example. It could do with some sprucing up.

Latest release:
https://img.shields.io/github/v/release/mattwhitfield/unittestgenerator?color=00A000

Last commit:
https://img.shields.io/github/last-commit/mattwhitfield/unittestgenerator?color=00A000

Build status:
https://img.shields.io/github/workflow/status/mattwhitfield/unittestgenerator/Extension%20build

Open issue count:
https://img.shields.io/github/issues/mattwhitfield/unittestgenerator

Features page doesn't really work as a table - split it out
Docs don't have a link to the github repo
Contributing not linked to in the documentation sections
Contributing doesn't have a bunch of useful info - it does have code map, but nothing around expectations etc
Contributing should be added as CONTRIBUTING.md to the root of the repo
Docs don't really call out that per-member generation is a thing

It would be good to generate tests for record types