Over the last few weeks, I've been exploring the functionality of XUnit. For anyone who doesn't know, XUnit is one of the unit testing frameworks that are available for .NET.
Here are some of the topics I'm going to cover.
How to set up a test project
In-order to create a test, you need to first set up an XUnit project. You should be able to do that in Visual Studio by creating a new project.
Within that project, you can set up a class and create methods within that class.
But how does XUnit know which tests it needs to run? Well you can apply the "Fact" attribute to each method that you wish XUnit to run. XUnit will then know to run this test.
As you can see from the above example, I've created two methods. The TestPattern method has the "Fact" attribute assigned to it. Inside that method, there are a number of Assert calls within it. This is where you conduct your tests. XUnit allows you to test on many different things, and here is an example of some of the Assert calls that can be made:
- Contains - Whether a string contains a certain word
- Empty - Whether an IEnumerable is empty
- Equal - Pass in an expected and actual value
- IsNotNull - Pass in an object to see if it has been initalised
- True - Pass in a condition to see if it's true
How each test runs
Even if you have multiple test methods in a test class, each test will always initalise a new instance of the test class. This means that if you wish to run some code before your test commences, you can do so in the constructor.
So what if you want to run some code after a test has progressed? You may wish to log that the test has completed. Well you can inherit the IDisposable interface, and include the Dispose method.
Using the same test for multiple values
If you wish to test multiple values in the same test, rather than creating additional methods to accommodate for this, you can use the "Theory" attribute.
The "Theory" attribute is the same as the "Fact" attribute in the sense that XUnit knows the method is a test. But you have to include additional attributes to a method to allow to pass in multiple values.
One way you can do this is with the "InlineData" attribute. The "InlineData" attribute allows you to pass in an object array with each index representing a parameter in the method. And you can include multiple "InlineData" attributes per method.
In the example below, I've included two "InlineData" attributes. Each "InlineData" attribute has an array with three integers. Each of these integers represent the parameters for the test method in ascending order.
You can use the "InlineData" attribute, or you can use the "MemberData" and "ClassData" attribute. The "MemberData" attribute allows you to return your parameter data from a method by returning an IEnumberable<object>. The "ClassData" does the same as "MemberData", but you can return your data in a seperate class and inherit the IEnumberable<object>.
More to come
These are just some of the basics for XUnit. As I start to use the unit testing framework more, I will fill you in on some of the features it has.