Associate automated tests with test cases
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
Visual Studio 2022 | Visual Studio 2019 | Visual Studio 2017 | Visual Studio 2015
Consider using Visual Studio to associate automated tests with a test case when:
- You created a manual test case that you later decide is a good test to automate, but you still want to be able to run that test as part of a test plan. Tests can be run in the CI/CD pipeline by choosing the test plan or test suite in the settings of the Visual Studio Test task. Automated tests can also be run from the Test Plans web portal. If you're using XAML builds, you can also run these automated tests by using Microsoft Test Manager.
- You want to enable end-to-end traceability of requirements. If your test cases are linked to requirements or user stories, the results of the test execution can be used to establish the quality of those requirements.
Prerequisites
| Category | Requirement |
|---|---|
| Project access | Project member. |
| Access levels | - To view test-related work items or run test cases: At least Basic access. Users with Stakeholder access have no access to Test Plans. - To exercise the full range of test-related features: Basic + Test Plans access level or one of the following subscriptions: - Enterprise - Test Professional - MSDN Platforms |
| Permissions | - To add or modify test plans, test suites, test cases, or other test-based work item types: Edit work items in this node permission set to Allow under the corresponding Area Path. - To modify test plan properties such as build and test settings: Manage test plans permission set to Allow under the corresponding Area Path. - To create and delete test suites, add and remove test cases from test suites, or change test configurations associated with test suites: Manage test suites permission set to Allow under the corresponding Area Path. - Project-level permissions that you might need include: - To view, create, or delete test runs: View test runs, Create test runs, and Delete test runs permission set to Allow. - To manage test configurations or test environments: Manage test configurations and Manage test environments. - To add new tags to test-based work items: Create tag definition permission set to Allow. - To move test-based work items out of a project: Move work items out of this project permission set to Allow. - To delete or restore test-based work items: Delete and restore work items permission set to Allow. - To permanently delete test-based work items: Permanently delete work items permission set to Allow. |
For more information, see Manual test access and permissions.
Create a test project and build pipeline
Do the following steps to create a test project and build pipeline.
- Create a test project containing your automated test. What types of tests are supported?
- Check your test project into an Azure DevOps.
- Create a build pipeline for your project and ensure that it contains the automated test. What are the differences if I'm still using a XAML build?
Associate your test
Open your solution in Visual Studio Enterprise or Professional 2017 or a later version.
If you don't know the identifier of the work item for the test case, locate the test case in Azure Test Plans , or query for the work item in the Work hub.
When you know the identifier of the work item for the test case:
If you're using Visual Studio 2017 or later version, do the following steps to associate your tests.
- If the Test Explorer window isn't displayed, open it from the Test | Windows menu.
- If your tests aren't displayed in Test Explorer, build the solution.
- In Test Explorer, select the test method you want to associate and choose Associate to Test Case.
- In the dialog that opens, type the test case identifier and choose Add Association, then choose Save.
The dialog shows a list of test cases currently associated with the selected test method. You can't associate more than one test method with a test case, but you can associate a test method with more than one test case.
If you're using the build and release services in Azure DevOps, not a XAML build, you can run associated tests in the build and release pipelines by using theVisual Studio Test task. You can't run tests on-demand using Microsoft Test Manager unless you're using a XAML build.
The parameters in a test case aren't used by any automated test that you associate with a test case. Iterations of a test case that use these parameters are for manual tests only.
For more information, see the following articles:
- Add files to the server
- Continuous integration on any platform
- Recording and Playing Back Manual Tests
- Use UI Automation To Test Your Code
FAQs
See the following frequently asked questions (FAQs).
Q: What types of tests are supported?
A: The following capabilities and limitations exist for each test type:
- Coded UI test, Selenium tests, and unit tests written using Version 1 of the MSTest framework can be associated with a test case.
- Tests that use MSTest v2, NUnit, and xUnit frameworks can be associated with a test case work item when using Visual Studio 15.9 Preview 2 or later. However, these tests can't be run using Microsoft Test Manager and XAML builds.
- Tests that use the .NET core framework can be associated with a test case work item when using Visual Studio 15.9 Preview 2 or later. Run the .NET core tests. The appropriate target framework must be specified in a .runsettings file. However, these tests can't be run using Microsoft Test Manager and XAML builds.
- Tests that use other test frameworks such as Chutzpah (for JavaScript tests such as Mocha or QUnit), or Jest cannot be associated with a test case.
- Generic tests are not available in Visual Studio 2022.
Q: What are the differences if I'm still using a XAML build?
A: If you're using a XAML build in Azure Pipelines, you can run tests that you associated in a Build-Deploy-Test workflow using a Lab environment. You can also run tests using Microsoft Test Manager and a Lab environment.
Q: Can I configure work items to open in Visual Studio?
A: Yes. If you want test work items to open inside Visual Studio instead of the default Azure Pipelines UI in your web browser, change the Work Items | General setting from the Tools | Options menu in Visual Studio.
