| title | description | ms.assetid | ms.prod | ms.technology | ms.topic | ms.manager | ms.author | author | ms.date | monikerRange |
|---|---|---|---|---|---|---|---|---|---|---|
FAQs and problem solutions |
FAQs for manual testing topics for Azure DevOps and Microsoft Team Foundation Server (TFS) |
C9467223-4513-4F46-812C-44FFE2B27F28 |
devops |
devops-test |
reference |
jillfra |
ahomer |
alexhomer1 |
04/24/2019 |
>= tfs-2015 |
[!INCLUDE version-inc-vs-all]
A: Yes, open the test plan from the shortcut menu and rename it.
A: Yes, do this from the shortcut menu for the test plan.
See also Delete test artifacts
A: Yes, you can create a static test suite that can contain any type of test suites - just like folders. Drag test suites to group them in a static test plan. Drag and drop tests to reorder them.
A: Use a query to group together test cases that have a particular characteristic, for example, all tests that have Priority=1. The suite will automatically include every test case that is returned by the query that you define.
A: Yes. For test plans, use this API. For test suites, use this API. We plan to expose these capabilities through the out-of-box UI in a future release.
A: Yes, you can export test plans, test suites, and test cases. Select the details that you want in the report. Then email or print this report for review.
Change the test case fields in the report by adding or removing columns from the list view of the test suite.
A: Yes, choose Print in the Export dialog box, then choose Cancel in the Print dialog box. This 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.
A: You can only do this if you are using an on-premises Team Foundation Server. You can edit the XSLT file.
A: Yes, you can track changes to test plans and test suites. Open the work item for the test plan or test suite, then view the work item history.
For test suites, other actions are tracked in the Test Suite Audit field. For example, adding and removing test cases from a test suite are tracked in this field.
A: Yes. Open the test case from its shortcut menu.
Then rename it.
Or permanently delete it.
See also Delete test artifacts
A: Yes, press Shift+Enter in the action or expected results field to add an extra line.
A: Select a test step. Press Alt+P to insert a new test step above the selected step.
A: Yes, use the grid view when you add test cases to the test suite.
On the grid shortcut menu, you can add, delete, or clear rows.
Switch between Grid and List views using the View menu at the right of the window.
Note: Do not use the Team plugin for Excel to add or update test case work items. Excel cannot parse the format used to store test steps, and in some cases this may affect the formatting of the test case work items.
A: Yes, switch the view from List to Grid. The grid shows all the test cases for the current test suite and all the test steps for those cases. This is a helpful view if you want to review your test cases with other team members. When you review, you can update and add new test cases.
Or, you can filter and sort the test cases in list view. Then select just the ones that you want to bulk edit using the grid.
To return to the test suite view, switch the view from Grid back to List.
A: Yes, copy the columns from Excel that you want to use for the title, action, and expected results fields. No column formatting, other than multiline, is copied from the worksheet. Paste these columns into the grid view, edit if necessary, and save them. (This is supported only with Internet Explorer and Chrome browsers.)
A: Yes, copy the data from the grid and paste it into your Excel worksheet. No test step formatting, other than multiline, is copied into the worksheet. (This is supported only with Internet Explorer and Chrome browsers.)
A: Yes, in List view use the column options to select the fields in the test case work item.
You can then view and edit these fields when you switch to the grid view.
A: Yes, you can reorder manual test cases in static suites, requirement-based suites, and query-based suites. Choose Order tests on the tool bar, then drag and drop one or more tests. Or open the shortcut menu for a test to move it to the top or to another position. After reordering the tests, you can sort them by the Order field and then run them in that order with the web runner.
A: Yes, you can tag test cases in a suite with any tag that you want. For example, tag all the tests related to login so that you can rerun these tests if a bug is fixed for the login page. Then you can filter on that tag from [!INCLUDE test-hub-include].
You can add and edit tags when you edit a test case, or bulk edit tags in the grid view. You can also create suites based on queries when you use tags.
![In [!INCLUDE test-hub-include], on the Test Plans page, choose or add tags from the test case pane](/timothywarner/azure-devops-docs/blob/136b3f294ea84569e479b2831387c9de9bc5d76d/docs/test/_img/create-test-cases/TestHubTags.png)
A: Yes, choose the steps that you want to share. Find out more about sharing test steps.
A: Yes, choose a test step, and then add the parameter. Find out more about repeating test steps with different data.
A: Yes. That way, test cases with the same parameters can run with same data, so you get consistent results. To share parameter data, convert your existing parameters to shared parameters.
After you create a shared parameter set, open another test case, and add the shared parameter set to that test case. Find out more about sharing parameters.
Add, edit, and rename your shared parameter sets on the Parameters page. In the test cases pane, view the test cases that use those parameters.
Each shared parameter set is a work item. On the Properties page, you can view or make changes to this work item. For example, you can assign owners and track changes.
A: Yes, copy the data from your Excel spreadsheet and paste it into your shared parameters grid. You can also copy the data from your grid back into Excel, if necessary.
A: 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 includes all projects.
Click 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.
A: 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.
Q: Why do I see the wrong test suite and tests when I click 'View Tests' from the notification email about tests that are assigned to me?
A: This might happen if you were prompted to enter sign-in credentials for Azure DevOps when you clicked this link. Without signing out of Azure DevOps, click 'View Tests' again to see the correct test suite and tests.
A: Just select any test and choose Run.
A: Yes, select a test suite and choose Run. This runs all the active tests in the test suite. If you haven't run a test yet, its state is active. You can reset the state of a test to active if you want to rerun it.
A: Yes, Choose Run and then select Run with options.
Select the build you want from the drop-down list.
Any bug filed during the run will automatically be associated with the selected build, and the test outcome will be published against that build.
A: Yes, if you have the Test Manager for Azure DevOps. You can insert, move, or delete steps. Or you can edit the text itself. Use the edit icon next to the test step number to do this.
The tool to edit the test steps is shown.
A: If you are using Google Chrome or Firefox, you can use the web runner to take screenshots of the web app while testing. For Microsoft Internet Explorer or Microsoft Edge browsers, or for desktop app testing, you can download and use the Test Runner desktop client.
For more information, see Collect diagnostic data.
A: If you are using Google Chrome or Firefox, you can use the web runner capture your actions on the web app as image logs while testing. For Microsoft Internet Explorer or Microsoft Edge browsers, or for desktop app testing, you can download and use the Test Runner desktop client.
For more information, see Collect diagnostic data.
A: If you are using Google Chrome or Firefox, you can use the web runner to capture screen recordings of your web and desktop apps while testing. For Microsoft Internet Explorer or Microsoft Edge browsers, or for desktop app testing, you can download and use the Test Runner desktop client.
For more information, see Collect diagnostic data.
A: Learn more here.
A: The Test Runner desktop client can be downloaded from here.
A: The Test Runner desktop client is currently supported only on Windows.
A: No. The Test Runner desktop client does not collect any user-identifiable data and so, in adherence to the Microsoft Privacy policy, no opt-out mechanism is provided.
A: Yes, see the Offline Test Execution extension.
A: Yes, select the test case within a test suite and then choose to view the test details pane.
View the recent test results for this test case.
A: 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.
A: You need at least a Basic access to create charts.
A: Select the option you want from the chart's context menu.
A: Learn more here.
Q: Are parameters the best way to specify that the test should be run on different operating system platforms? And with different browsers, databases, and so on?
A: It's better to use test configurations for that. With test case parameters, you run the different parameter values one after another, which makes it difficult to switch from one platform to another.
A: Yes. You set the parameter values in the test cases where you use the shared steps.
A: Yes. Copy the data from your Excel spreadsheet and paste it into your shared parameters grid. You can also copy the data from your grid back into Excel if you need to.
A: 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.
A: 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. Learn more.
A: By default, this is turned off because 10 builds can happen very quickly, especially with continuous integration builds. Test results are often deleted before you can analyze them.
A: Like this:
A: Yes. But don't forget that if you edit shared steps, the changes appear in every place you use them.
A: Yes. You provide values for the parameters in the test cases where the shared steps are used.
You don't have to provide values in the shared steps definition. However, you can provide one default row of values, which is used when you create an action recording of a standalone shared step.
A: The Test & Feedback extension is currently available for Google Chrome and Mozilla Firefox version 50.0 and higher. Edge support is planned.
Some browser versions do not currently support all the features of the Test & Feedback extension.
| Feature | Chrome | Firefox |
|---|---|---|
| Capture screenshots with inline annotations | Yes | Yes |
| Capture notes | Yes | Yes |
| Capture screen recordings | Yes | No |
| Capture page load data | Yes | No |
| Capture user actions log | Yes | No |
| Capture system information | Yes | No |
| Create bugs | Yes | Yes |
| Create tasks and test cases | Yes | Yes |
| Create feedback requests | Yes | Yes |
| Export session report for sharing | Yes | Yes |
| End-to-end traceability for workitems | Yes | Yes |
| Simplified bug and task tracking and triaging | Yes | Yes |
| View and get insights from sessions | Yes | Yes |
| View similar existing bugs | Yes | Yes |
| Test app on devices using cloud providers such as Perfecto | Yes | No |
| Manage feedback requests | Yes | Yes |
For more details, see [Visual Studio Marketplace](https://marketplace.visualstudio.com/items/ms.vss-exploratorytesting-web), Azure DevOps tab.
A: The video recordings created by the Test & Feedback extension can be viewed in Google Chrome browser and in the VLC Video Player.
A: The Test & Feedback extension supports Team Foundation Server 2015 and later. All users, including stakeholders, can use the extension in Connected mode with all the functionality except session insights and the request and provide feedback flow, which are supported only for TFS 2017.
Q: Can I edit an existing bug instead of creating a new bug when using the Test & Feedback extension?
A: Yes, the extension automatically shows bugs that may be related to the one you are creating and allows you to add your screenshots, notes, and videos to this existing bug. For more details, see Add findings to existing bugs with exploratory testing.
Q: On Google Chrome, the mouse offset towards the left makes it difficult to use. Do you have a workaround?
A: The workaround is:
- Navigate to chrome://flags/#enable-use-zoom-for-dsf
- Search for 'Use Blink's zoom for device scale factor'
- Change it to Disabled
[!INCLUDE help-and-support-footer]