Access and permissions FAQs

Query-based test suites use a query to group together test cases that have a particular characteristic, for example, all tests that have Priority=1. The test suite automatically includes every test case that is returned by the query.

Yes. Depending on the action you want to take, you can copy or clone test plans and import or clone test suites. To learn how, see Copy or clone test plans, test suites, and test cases.

Yes* Choose Print in the Export dialog box, then choose Cancel in the Print dialog box. This option displays the data in the report. Select all the text, then copy and paste it into a Word document, if you want. All the formatting in the report is retained.

The test case still exists in your project, but the test case is removed from the test suite. Also, it's no longer linked to the backlog item for that test suite.

Yes. See Copy test cases.

Yes. Press Shift+Enter in the action or expected results field to add an extra line.

Select a test step. Press Alt+P to insert a new test step above the selected step.

Select a test case, then view the test suites details. The Associated test suites pane shows you any test suite for any test plan that contains this test case. This view includes all projects.

Select the associated test suite to view it. To view the project and the test plan for that test suite, move your pointer over the test suite.

See Delete test artifacts.

For test case charts, if a test case has been added to multiple test suites in a plan then it's only counted once. For test result charts, each instance of a test that is run is counted for each of the test suites separately.

To create charts, you need to be assigned Basic access or higher.

Choose Configure and the option you want from the chart's context menu.

It's better to use test configurations. With test case parameters, you run the different parameter values one after another, which makes it difficult to switch from one platform to another. For more information, see Test different configurations.

For projects created before October 2015, Azure DevOps doesn't delete results from automated tests and manual tests unless you change the retention limit.
For new projects created after October 2015, Azure DevOps deletes all test results after one year (365 days), unless you chose to indefinitely retain a build associated with those results.

See Set test retention policies.

By default, a XAML build pipeline is set up to delete builds older than the 10 most recent builds. But related test results aren't automatically deleted when those builds are deleted.

For more information, see Create or edit a build definition.

By default, this behavior is turned off because 10 builds can happen quickly, especially with continuous integration builds. Test results are often deleted before you can analyze them.

See Set retention policies for builds, releases, and tests.

YOu can view the video recordings created by the Test & Feedback extension in Google Chrome browser and in the VLC Video Player.

The Test & Feedback extension supports Team Foundation Server 2015 and later versions. All users, including users granted Stakeholder access, can use the extension in Connected mode. Functionality associated with session insights and the request and provide feedback flow require Team Foundation Server 2017 or later versions.

Yes, the extension automatically shows bugs that may be related to the one you're creating and allows you to add your screenshots, notes, and videos to this existing bug. For more information, see Add findings to existing bugs with exploratory testing.

Follow this procedure:

1. Navigate to chrome://flags/#enable-use-zoom-for-dsf.
2. Search for 'Use Blink's zoom for device scale factor'.
3. Change it to Disabled.

Related articles

• Run automated tests from test plans
• Run manual tests
• Track test status
• Repeat a test with different data
• Set test retention policies
• Install the Test & Feedback extension