Install-Package xunit.runner.visualstudio) Rebuild to make sure xunit.runner ends up in the output dir. Configure xunit.runner.json file to copy always or preserve newest in visual studio so that gets copied on bin folder (as any appsetings.json file) I've read that you can place an assembly attribute in the assemblyInfo.cs file that by the way it seems that was replaced by the plain csproj so I'm a bit confused. Set CopyToOutputDirectory=PreserveNewest automatically for xunit.runner.json area: Core framework type: Feature #2185 opened Nov 2, 2020 by kzu. This ensures that our application running in an integration test can still read the appsettings.json file. Please read more in the link Step 1 : Create a xunit.runner.json file to the root folder of the test project. Console Runner. Nuget: Go to Package Manager Console (Alt-T,N,O) and . We need to turn off shadow copying, so any separate files like appsettings.json are placed in the right place beside the application DLL file. This is integrated with Visual Studio 2017 15.9+ update and Visual Studio 2019 version. Having said that, your question about running xUnit tests in sequence does have an answer! Includes runner reporters for TeamCity, AppVeyor, Verbose and Quiet output for test runners. Close Test Explorer <- this was the missing bit for me. This test runner shows the status of the tests. It can run multiple assemblies at the same time, and command line options can be used to configuration the parallelism options used when running the tests. xunit.runner.json. true: this will enable the parallelize run of Xunit tests. The VS Test output pane contains information about load failures (see below). Note the version_in_path: true bit is important. nuget xunit.runner.visualstudio version_in_path: true. depending on a static property that is modified by each test) is regarded as bad practice. Step 2 : Copy paste the below data in to the file. All good unit tests should be 100% isolated. The Microsoft.Net.Test.Sdk package is the MSBuild targets and properties for building .NET Test projects. The console runner in v2 is capable of running unit tests from both v1 and v2. Many thanks to all the developers of xunit and xunit.runner.wpf! I'm using xUnit. {“parallelizeTestCollections”:false} false : this will disable the parallelize run of XUnit tests. However, the mentioned assemblies are in the same directory as the test assembly and any needed binding redirects are in place. The xunit.runner.visualstudio package is a Test Explorer for framework. xUnitRevit uses speckle.xunit.runner.wpf which is a fork of xunit.runner.wpf, it allows to easily develop and run xUnit tests in Revit. To use JSON-based configuration in a desktop or PCL unit test project, you need to take two steps: Add a new JSON file to root of your test project. Name the file xunit.runner.json. It's as if information in the xunit.runner.json file or {test assembly}.config files is ignored. Using shared state (e.g. For dotnet core, see Dimitry's answer regarding xunit.runner.json. (If your version of Visual Studio does not have "JSON file" as an option for a new file, just choose to add a text file, and make sure it has the right name.) If I reference the xunit.runner.visualstudio package as a dependency in my project.json (example project.json below), the dll xunit.runner.visualstudio.testadapter is not included in the build output produced by dotnet build..