Why Write Unit Tests?
Unit testing is a fast way to test code automatically before releasing it to production. Unlike other testing, unit tests should be designed to run in milliseconds, without any external dependencies. Without running unit tests, there is a chance for regression in code and that means unexpected bugs.
Why xUnit.net?
Using xUnit.net is a choice I made because it's free, open source and is supported by the .NET Foundation.
I wanted to use it instead of MSTest because it offers a more useful syntax when testing multiple scenarios in a single method. For example. you can have attributes on your method that reuse the same method with xUnit.net Theories.
Example:
How To Add xUnit.net To A Solution
Adding an xUnit.net project is easy in Visual Studio 2017 when using .NET Core. You just right click on your project, add a new project and find the "xUnit Test Project (.NET Core)".
Once you have the project, you can add a test runner to run the tests in Visual Studio. To do that, install the "xunit.runner.console" and "xunit.runner.visualstudio" xUnit NuGet packages.
Running xUnit.net Tests From The Command Line
Everything must be able to be automated to work in a continuous deployment release process. With xUnit.net, running the tests is quite easy. You simply run a single command and optionally specify the path to the unit test project, if not currently in that directory.
Example:
This will output the results of your test run to the console.
