First look at testing tools in Visual Studio
Applies to: Visual Studio Visual Studio for Mac Visual Studio Code
Visual Studio testing tools can help you and your team develop and sustain high standards of code excellence.
Unit testing is available in all editions of Visual Studio. Other testing tools, such as Live Unit Testing and IntelliTest, are only available in Visual Studio Enterprise edition. For more information about editions see Compare Visual Studio IDEs.
The Test Explorer window helps developers create, manage, and run unit tests. You can use the Microsoft unit test framework or one of several third-party and open source frameworks.
- Get started with unit testing
- Unit test basics
- Run unit tests with Test Explorer
- Test Explorer FAQ
- Install third-party unit test frameworks
Visual Studio is also extensible and opens the door for third-party unit testing adapters such as NUnit and xUnit.net. In addition, the code clone capability goes hand-in-hand with delivering high-quality software by helping you identify blocks of semantically similar code that may be candidates for common bug fixes or refactoring.
Live Unit Testing
Live Unit Testing automatically runs unit tests in the background, and graphically displays code coverage and test results in the Visual Studio code editor.
Live unit testing is available in Enterprise edition only and is only supported for .NET code.
IntelliTest automatically generates unit tests and test data for your managed code. IntelliTest improves coverage and dramatically reduces the effort to create and maintain unit tests for new or existing code.
IntelliTest is available in Enterprise edition only. It is supported for C# code that targets the .NET Framework. .NET Core and .NET Standard are not currently supported.
- Generate unit tests for your code with IntelliTest
- IntelliTest – One test to rule them all
- IntelliTest reference manual
Code coverage determines what proportion of your project's code is actually being tested by coded tests such as unit tests. To guard effectively against bugs, your tests should exercise or "cover" a large proportion of your code.
Code coverage is available in Enterprise edition only.
Code coverage analysis can be applied to both managed and unmanaged (native) code.
Code coverage is an option when you run test methods using Test Explorer. The results table shows the percentage of the code that was run in each assembly, class, and method. In addition, the source editor shows you which code has been tested.
- Use code coverage to determine how much code is being tested
- Unit testing, code coverage and code clone analysis with Visual Studio (Lab)
- Customize code coverage analysis
- Microsoft.CodeCoverage.Console tool
Microsoft Fakes help you isolate the code you're testing by replacing other parts of the application with stubs or shims.
Microsoft Fakes are available in Enterprise edition only and is supported only for .NET code.
User interface testing with Playwright
Playwright is recommended for generic browser-based UI testing.
User interface testing with Coded UI and Selenium
Coded UI tests provide a way to create fully automated tests to validate the functionality and behavior of your application’s user interface. They can automate UI testing across a variety of technologies, including XAML-based UWP apps, browser apps, and SharePoint apps.
Coded UI is a deprecated feature.
Whether you choose best-of-breed Coded UI Tests or generic browser-based UI testing with Playwright, Visual Studio provides all the tools you need.
Submit and view feedback for