C# NUnit parameterized TestCaseSource value identification

Question

I am using TestCaseSource on NUnit 2.6.1 to test the same Asserts with different object class constructor parameters.

I mean,

[Test, TestCaseSource("myConstructorsForMale")}
public void CheckMale(Person p) 
{
     Assert.That(p.IsMale);
}

static Person[] myConstructorsForMale = 
                     {
                         new Person("John"),
                         new Person(isMale=true),
                         new Person("Doe")
                     };

Ok, all is runing fine, but this is the result I received on the NUnit Console:

• CheckMale
  • CheckMale(Person)
  • CheckMale(Person)
  • CheckMale(Person)

So I don't know what is the test executed on every iteration and if any of them fail I cannot get what is the failing test.

My question is: Are there any way to identify with a comment or something similar what is the parameter being passed to the test ? (in TestCaseSource Attribute way of do)

Thanks.

Answer 1

If case of using 'native' NUnitor ReSharper as a test runner you can override ToString method so that you have good Person definitions. For example, your testing code could look like:

public class PersonTests
{
    [Test, TestCaseSource("myConstructorsForMale")]
    public void CheckMale(Person p)
    {
        Assert.That(p.IsMale);
    }

    static Person[] myConstructorsForMale = 
                 {
                     new Person("John"),
                     new Person{IsMale=true},
                     new Person("Doe")
                 };
}

Person class could be like:

public class Person
{
    public Person(string name)
    {
        this.Name = name;
    }

    public Person() { }

    public string Name { get; set; }
    public bool IsMale { get; set; }

    public override string ToString()
    {
        return string.Format("Name:{0};IsMale:{1}", Name, IsMale);
    }
}

The result window will look like this:

I also checked it on native NUnit test runner, which you probably use. It also displays Persons nicely: