Last year I open sourced some code that allowed you to power your xUnit theories from a custom section in your application configuration file. I have now updated that project to support xUnit 2.0, and also to allow for an optional name attribute to be set on each data set.
<testData>
<tests>
<add name="SampleProject.Class1.Main">
<data>
<add index="0" name="Optional" p0="Hello" p1="World" />
<add index="1" name="Cows" p0="Goodnight" p1="Moon" />
</data>
</add>
</tests>
</testData>
Enjoy,
Tom
I've said it before and I'll say it again, I love xUnit!
In particular, I love xUnits support for data driven tests. It offers several different options for ways to power a data driven unit test right out of the box. Best of all, xUnit allows for easy extensibility.
I have written some simple extensions for xUnit that allow you to power your data driven tests from your configuration file. Not only that, but it allows you to optionally provide default data using inline attributes when no configuration is available.
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<section name="testData"
type="Xunit.Extensions.Configuration.TestDataSection,xunit.extensions.config"/>
</configSections>
<testData>
<tests>
<add name="Demo.Tests.Basic">
<data>
<add index="0" p0="1" />
</data>
</add>
<add name="Demo.Tests.FromConfig">
<data>
<add index="0" p0="4" />
</data>
</add>
</tests>
</testData>
</configuration>
namespace Demo
{
public class Tests
{
[Theory]
[ConfigData]
public void Basic(int i)
{
// This theory data comes from the config file.
Assert.Equal(1, i);
}
[Theory]
[ConfigOrInlineData(2)]
public void FromInline(int i)
{
// This theory data comes from the attribute.
Assert.Equal(2, i);
}
[Theory]
[ConfigOrInlineData(3)]
public void FromConfig(int i)
{
// This theory data comes from the config file
// instead of the attribute.
Assert.Equal(4, i);
}
}
}
Enjoy,Tom
Inversion of control is great because it makes your code more testable; but you usually still have to write tests for each implementation of your interfaces. So what if your unit testing framework could just work directly with your container to make testing even easier? Well, xUnit can!
Below we define a custom data source for our xUnit theories by extending the InlineDataAttribute. This allows our data driven unit tests to resolve types via a container, and then inject those resolved objects straight into our unit tests.
Bottom line: This allows us to test more with less code!
The rest of post is very code heavy, so I strongly recommend that you start out by taking a look at sections 1 and 2 to get an idea of what we are trying to accomplish. :)
