Overloads cause test method name collision through duplicates

[chuck-flowers]

Currently if there is a method with overloads multiple test methods with the same name are generated which causes the compilation of the test methods to fail.

Example:
Source Code

public class Foo
{
    public void Bar()
    {
        //Does stuff that needs testing
    }

    public void Bar(int i)
    {
        //Does stuff that needs testing
    }
}

Generated Test Code

public class FooTests
{
    [Fact]
    public void BarTest()
    {
        //Test code goes here
    }

    [Fact]
    //This is a duplicate definition!!! Won't compile
    public void BarTest()
    {
        //Test code goes here
    }
}

[chuck-flowers]

Proposed Solution

One possible way to fix this issue might be to have the generated tests accept parameters that match the signature of the method they are testing.

Potential Problems

This would likely warrant decorating overloads with parameters as Theories. This makes more assumptions about how people want their test code generated.

Example

The following is an example of how the source code would be generated with the new behavior in the case outlined by the initial comment.

Source Code

public class Foo
{
    public void Bar()
    {
        //Does stuff that needs testing
    }

    public void Bar(int i)
    {
        //Does stuff that needs testing
    }
}

Generated Test Code

public class FooTests
{
    [Fact]
    public void BarTest()
    {
        //Test code goes here
    }

    [Fact]
    public void BarTest(int i)
    {
        //Test code goes here
    }
}