-
Notifications
You must be signed in to change notification settings - Fork 2.5k
/
Copy pathreference-qa.yml
214 lines (156 loc) · 10.5 KB
/
reference-qa.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
### YamlMime:FAQ
metadata:
title: Test plans frequently asked questions
description: Learn about frequently asked questions (FAQs) on test plans in Azure DevOps.
titleSuffix: Azure Test Plans
ms.service: azure-devops-test-plans
ms.custom: UpdateFrequency3
ms.author: jeom
author: raviLiftr
ms.topic: FAQ
monikerRange: '<= azure-devops'
ms.date: 02/16/2022
title: Access and permissions FAQs
summary: |
[!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
Find answers to frequently asked questions when using Azure Test Plans. For how-to guides, see the following articles:
- [Create test plans and test suites](create-a-test-plan.md)
- [Create manual test cases](create-test-cases.md)
- [Track test status](track-test-status.md)
- [Repeat a test with different data](repeat-test-with-different-data.md)
- [Set test retention policies](how-long-to-keep-test-results.md)
- [Install the Test & Feedback extension](perform-exploratory-tests.md)
<a name="testplans" />
<a name="query-based-suites"></a>
sections:
- name: Test plans and test suites
questions:
- question: What are query-based test suites?
answer: |
<a name="query-based-suites"></a>
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 returned by the query.
<a name="copyclonetce"></a>
- question: Can I copy or clone test plans and test suites?
answer: |
**Yes**. Depending on your desired action, 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](copy-clone-test-items.md).
> [!NOTE]
> - You can export a maximum of 75 test suites in a single operation. The email supports up to 1 MB of data.
> - You can't export test plan attachments.
- question: Can I just view test plan data I export, or copy it to a Word document?
answer: |
**Yes**. Select **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.
- question: What happens when I delete a test case from a requirement-based test suite?
answer: |
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.
<a name="ViewAssignedTests" />
- question: Why do I see the wrong test suite and tests when I select View Tests from the notification email about tests that are assigned to me?
answer: |
This situation might happen if you were prompted to enter credentials for Azure DevOps when you clicked the link.
Without signing out of Azure DevOps, select **View Tests** again to see the correct test suite and tests.
<a name="testcases" />
<a name="create-manual-test-cases" />
- name: Test cases
questions:
- question: Can I copy test cases from one project to another?
answer: |
**Yes**. See [Copy test cases](copy-clone-test-items.md#copy-test-case). For Azure DevOps Server 2020 and later versions, you can copy test cases from a project to a test suite, or you can use the [Grid view to copy and paste test cases](copy-clone-test-items.md#copy-paste) from one suite to another. Optionally, you can [bulk import and export test cases](copy-clone-test-items.md#bulk-import-export).
- question: Can I add an extra line to a test step?
answer: |
**Yes**. Press **Shift**+**Enter** in the action or expected results field to add an extra line.
- question: How do I insert a test step into a test case?
answer: |
Select a test step. Press **Alt**+**P** to insert a new test step above the selected step.
<a name="add-multiple-test-cases"></a>
- question: How can I find out if a test case was added to other test suites?
answer: |
::: moniker range=">=azure-devops-2020"
Select a test case in the **Define** tab. Right-click or select **More options** to open the context menu, and then select **View linked items**.
In the **Linked Items** dialog box, select **Test Suites** to see the test suites linked to the test case. Double-click a test suite to open it.
::: moniker-end
- question: How do I delete a test case or other test artifacts?
answer: |
See [Delete test artifacts](../boards/backlogs/delete-test-artifacts.md).
<a name="runtests"></a>
<a name="qanda"></a>
<a name="trackstatus"></a>
- name: Test status tracking charts
questions:
- question: How is data shown in the charts for test cases that are in multiple test suites?
answer: |
For test case charts, if a test case gets added to multiple test suites in a plan, then the test only gets counted once.
For test result charts, each instance of a test that is run is counted for each of the test suites separately.
- question: Who can create charts?
answer: |
To create charts, you need to be assigned at least Basic access.
- question: How can I edit or delete a chart?
answer: |
Choose :::image type="icon" source="../media/icons/actions-icon.png" border="false"::: **Configure** and the option you want from the chart's context menu.
:::image type="content" source="media/track-test-status/test-chart-options-context-menu.png" alt-text="Screenshot of test tracking chart configure options menu.":::
<a name="repeatdifferent"></a>
- name: Test configurations
questions:
- question: 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?
answer: |
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](test-different-configurations.md).
<a name="manageresults"></a>
- name: Test results and retaining test data
questions:
- question: What are the default retention limits?
answer: |
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.
- question: How do I control how long I keep my test data?
answer: |
See [Set test retention policies](how-long-to-keep-test-results.md).
- question: What is the default test retention policy for XAML builds?
answer: |
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](/previous-versions/visualstudio/visual-studio-2013/ms181716(v=vs.120)).
- question: Why isn't test data deleted for XAML builds by default?
answer: |
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.
<a name="keep-build-indefinitely"></a>
- question: How do I keep a build indefinitely?
answer: |
See [Set retention policies for builds, releases, and tests](../pipelines/policies/retention.md).
<a name="tandfext" />
<a name="recording-playback" />
- name: Test & Feedback extension
questions:
- question: How do I play the video recordings I created with the extension?
answer: |
You can view the video recordings created by the Test & Feedback extension in [Google Chrome](https://www.google.com/chrome/) browser and in the [VLC Video Player](https://www.videolan.org/vlc/download-windows.html).
- question: Does the extension support Team Foundation Server?
answer: |
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.
<a name="addsimilar"></a>
- question: Can I edit an existing bug instead of creating a new bug when using the Test & Feedback extension?
answer: |
Yes, the extension automatically shows bugs that might 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](add-to-bugs-exploratory-testing.md).
- question: On Google Chrome, the mouse offset towards the left makes it difficult to use. Do you have a workaround?
answer: |
Do the following steps as a workaround.
1. Navigate to **chrome://flags/#enable-use-zoom-for-dsf**.
1. Search for 'Use Blink's zoom for device scale factor.'
1. Change it to **Disabled**.
additionalContent: |
## Related articles
- [Run automated tests from test plans](run-automated-tests-from-test-hub.md)
- [Run manual tests](run-manual-tests.md)
- [Track test status](track-test-status.md)
- [Repeat a test with different data](repeat-test-with-different-data.md)
- [Set test retention policies](how-long-to-keep-test-results.md)
- [Install the Test & Feedback extension](perform-exploratory-tests.md)