xunit.net

Is it better to have a unit-test project per solution or a unit-test project per project? With per solution, if you have 5 projects in the solution you end-up with 1 unit-test project containing tests for each of the 5 projects. With per project, if you have 5 projects in the solution you end-up with 5 unit-test projects. What is the right way? I think it's not the same question as Write Unit tests into an assembly or in a separate assembly? Assemblies are a packaging/deployment concern, so we usually split them out because we don't want to deploy them with our product. Whether you split them

I'm new to TDD and xUnit so I want to test my method that looks something like: List<T> DeleteElements<T>(this List<T> a, List<T> b); Is there any Assert method that I can use ? I think something like this would be nice List<int> values = new List<int>() { 1, 2, 3 }; List<int> expected = new List<int>() { 1 }; List<int> actual = values.DeleteElements(new List<int>() { 2, 3 }); Assert.Exact(expected, actual); Is there something like this ? xUnit.Net recognizes collections so you just need to do Assert.Equal(expected, actual); // Order is important You can see other available collection

TL;DR - I'm looking for xUnit's equivalent of MSTest's AssemblyInitialize (aka the ONE feature it has that I like). Specifically I'm looking for it because I have some Selenium smoke tests which I would like to be able to run with no other dependencies. I have a Fixture that will launch IisExpress for me and kill it on disposal. But doing this before every test hugely bloats runtime. I would like to trigger this code once at the start of testing, and dispose of it (shutting down the process) at the end. How could I go about doing that? Even if I can get programmatic access to something like

This question is about the unit testing framework xUnit.net . I need to run some code before any test is executed, and also some code after all tests are done. I thought there should be some kind of attribute or marker interface to indicate the global initialization and termination code, but couldn't find them. Alternatively, if I invoke xUnit programmatically, I can also achieve what I want with the following code: static void Main() { try { MyGlobalSetup(); RunAllTests(); // What goes into this method? } finally { MyGlobalTeardown(); } } Can anyone provide me a hint about how to

I'm running Watin tests with xUnit on CC.Net under Windows Server 2003. I have lots of tests that all run fine on development boxes with TestDriven.Net and on the server with the xUnit gui app. However, when CC.Net runs the tests (as part of an MSBuild task) the function ie.ContainsText("some text to find"); never returns the expected value. Other functions and properties on the IE object appear to work fine: Button(...).Click(), TextBox(...).Value, etc. I am aware that the service account needs "Allow service to interact with the desktop". I have tried this running CC service under Local

When using xunit.runner.visualstudio version 2.0.1 in Visual Studio 2015, the names of the tests show up fully qualified. Is there a way for the tests to show only the method name? Consider the following test: - namespace MySolution.Tests { public class MyTestClass { [Fact] public void ClassUnderTest_WhenDefaultConstructorUsed_SomePropertyIsNotNull() { *... test code in here* } } } In the Test Explorer this shows as: - MySolution.Tests.MyTestClass.ClassUnderTest_WhenDefaultConstructorUsed_SomePropertyIsNotNull Using MSTest/VSTest this will show up as: - ClassUnderTest