The situation has changed a little with xUnit.net 2. I know the question is about an earlier version, but as people will land here having performed the upgrade, I thought it was worth pointing this out. In order to see some kind of output in the test output in version 2 you will need to … Read more
You can also add it with json. In the root directory of your test project add a file called “xunit.runner.json”. Right-click the file, properties. Select “Copy if newer” for copy to Output directory. Then in the file enter this json: { “methodDisplay”: “method” } Note that you may1 require to restart the IDE in order … Read more
In xUnit 2.* this can be achieved using the TestCaseOrderer attribute to designate an ordering strategy, which can be used to reference an attribute that is annotated on each test to denote an order. For example: Ordering Strategy [assembly: CollectionBehavior(DisableTestParallelization = true)] public class PriorityOrderer : ITestCaseOrderer { public IEnumerable<TTestCase> OrderTestCases<TTestCase>(IEnumerable<TTestCase> testCases) where TTestCase : … Read more
Each test class is a unique test collection and tests under it will run in sequence, so if you put all of your tests in same collection then it will run sequentially. In xUnit you can make following changes to achieve this: Following will run in parallel: namespace IntegrationTests { public class Class1 { [Fact] … Read more
As far as I know, xUnit does not have a global initialization/teardown extension point. However, it is easy to create one. Just create a base test class that implements IDisposable and do your initialization in the constructor and your teardown in the IDisposable.Dispose method. This would look like this: public abstract class TestsBase : IDisposable … Read more
TL;DR your Test Classes must be public (but your Test Methods can be private and/or static) For reasons of efficiency, the xUnit authors have opted to not use BindingFlags.NonPublic when searching for Test Classes in the runner (the MSIL metadata tables don’t index private(/internal) classes to the same degree hence there is a significant performance … Read more
As of Nov 2015 xUnit 2 is out, so there is a canonical way to share features between tests. It is documented here. Basically you’ll need to create a class doing the fixture: public class DatabaseFixture : IDisposable { public DatabaseFixture() { Db = new SqlConnection(“MyConnectionString”); // … initialize data in the test database … … Read more
The controller’s User is accessed through the HttpContext of the controller. The latter is stored within the ControllerContext. The easiest way to set the user is by assigning a different HttpContext with a constructed user. We can use DefaultHttpContext for this purpose, that way we don’t have to mock everything. Then we just use that … Read more
I know this is an old thread, but I thought I’d post a vote for xUnit.NET. While most of the other testing frameworks mentioned are all pretty much the same, xUnit.NET has taken a pretty unique, modern, and flexible approach to unit testing. It changes terminology, so you no longer define TestFixtures and Tests…you specify … Read more
There are many xxxxData attributes in XUnit. Check out for example the MemberData attribute. You can implement a property that returns IEnumerable<object[]>. Each object[] that this method generates will be then “unpacked” as a parameters for a single call to your [Theory] method. See i.e. these examples from here Here are some examples, just for … Read more