The Visual Studio Test Platform is an open and extensible test platform that enables running tests, collect diagnostics data and report results. The Test Platform supports running tests written in various test frameworks, and using a pluggable adapter model. Based on user-choice, the desired test framework and its corresponding adapter can be acquired as a vsix or as NuGet package as the case may be. Adapters can be written in terms of a public API exposed by the Test Platform.
The Test Platform currently ships as part Visual Studio 2019, and in the .NET Core Tools Preview 3.
There are many ways to contribute to VSTest
- Submit issues and help verify fixes as they are checked in.
- Review the source code changes.
- Contribute features and fixes.
- Contribute to the documentation.
NOTE: When adding a new public API, always add it directly to the PublicAPI.Shipped.txt file. This helps us ensure we are always considering potential breaking changes (even between successive commits of un-released version) and avoids the burden of the unshipped to shipped commit.
- Test Platform Architecture
- Test Discovery Protocol
- Test Execution Protocol
- Adapter Extensibility
- Test Platform SDK
- Editors API Specification
- Data collection Protocol
- Translation Layer
- Editors API Revision Update
- TranslationLayer
- Source Information For Discovered Tests
- Test Session Timeout
- Test Adapter Lookup
- Packaging
- Telemetry
- Loggers Information From RunSettings
- Properties for TestCases in Managed Code
- Skip Default Adapters
- Disable Appdomain While Running Tests
- Improving Logic To Pass Sources To Adapters
- Code Coverage for .Net Core
- User Specified TestAdapter Lookup
- TestSettings Deprecation
- Blame Collector Options
VSTest can be built from within Visual Studio or from the CLI.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
VSTest platform is licensed under the MIT license
Please see issue tracking for a description of the workflow we use to process issues.
For more information on shipped and upcoming features/enhancements please refer to our Releases and Quarterly Checkin reports
![@dotnet-maestro[bot]](https://avatars.githubusercontent.com/in/16706?s=64&v=4){kind=small}
