You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/test/create-a-test-plan.md
+5-6
Original file line number
Diff line number
Diff line change
@@ -92,24 +92,23 @@ To delete a test plan, do the following steps.
92
92
In general, you create test plans to test requirements. Before you create a test plan, [define your backlog of requirements](../boards/backlogs/create-your-backlog.md).
93
93
94
94
1. From the web portal, open your project and go to **Test Plans**.
95
-
If you already have a test plan, choose**Test Plans** to go to the page that lists all test plans.
95
+
If you already have a test plan, select**Test Plans** to go to the page that lists all test plans.
96
96
97
97
98
98
99
-
2.In the **Test Plans** page, choose **New Test Plan** to create a test plan for your current sprint.
99
+
2.Select **New Test Plan**.
100
100
101
101
102
102
103
-
3. In **New Test Plan**, enter a name for the test plan.
104
-
Verify that the area path and iteration are set correctly, then choose **Create**.
103
+
3. Enter a name for the test plan, verify that the area path and iteration are set correctly, and then select **Create**.
105
104
106
105
107
106
108
107
### Rename a test plan
109
108
110
109
To rename a test plan, open it from the shortcut menu and rename it.
111
110
112
-
111
+
113
112
114
113
### Delete a test plan
115
114
@@ -190,7 +189,7 @@ You can track changes to test plans and test suites. Open the work item for the
190
189
191
190
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.
192
191
193
-
You can export test plans, test suites, and test cases.
Copy file name to clipboardExpand all lines: docs/test/create-test-cases.md
+41-57
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,7 @@ ms.date: 11/04/2021
21
21
22
22
Create manual test cases to check that each deliverable meets your users' needs. Manual test cases define individual steps testers perform, including steps that are shared across test cases. To test different data, you specify parameters for the test steps. For more information, see [Share steps between test cases](share-steps-between-test-cases.md) and [Repeat a test with different data](repeat-test-with-different-data.md). For an overview of test artifacts, see [Test objects and terms](test-objects-overview.md).
23
23
24
-
Organize your test cases by adding them to test plans and test suites. Then assign testers to run the tests.
25
-
26
-
For an overview of test artifacts, see [Test objects and terms](test-objects-overview.md).
24
+
Organize your test cases by adding them to test plans and test suites, and then assign testers to run the tests. For more information, see [Test objects and terms](test-objects-overview.md).
27
25
28
26
> [!NOTE]
29
27
> Test iterations are designed to support data-driven scenarios, not workflow-driven scenarios.
@@ -37,74 +35,62 @@ For an overview of test artifacts, see [Test objects and terms](test-objects-ove
37
35
<aname="createcase"></a>
38
36
39
37
## Create test cases
38
+
40
39
::: moniker range=">=azure-devops-2020"
41
40
1. If you haven't already, [create a test plan and requirement-based test suites](create-a-test-plan.md).
42
41
43
-
1. Select a requirement-based test suite.
44
-
To the right, select the **New Test Case** button.
42
+
2. Select a requirement-based test suite and select **New Test Case**.
45
43
46
44
47
45
48
-
If you have no existing test cases, the button appears in the lower right.
49
-
50
46
> [!NOTE]
51
-
> The [test suite](create-a-test-plan.md) shown here was created from a User Story work item in the team's backlog board.
52
-
> When you add a test case to this kind of suite, the test case is automatically linked to the backlog item.
53
-
> To create test cases this way, open the context menu for the work item and choose **Add test**.
47
+
> The [test suite](create-a-test-plan.md) shown here was created from a User Story work item in the team's backlog board. When you add a test case to this kind of suite, the test case automatically links to the backlog item. To create test cases this way, open the context menu for the work item and choose **Add test**.
54
48
55
-
1. In the new work item, enter a title. Select the**Click or type here to add a step** option.
49
+
3. In the new work item, enter a title and select**Click or type here to add a step**.
56
50
57
51
58
52
59
-
Add test steps with a description of the action required to carry out the test and the expected results so that any team member can run the test.
60
-
You can add attachments to a step if you want.
61
-
Repeat until you add all the steps for the test.
62
-
63
-
> [!NOTE]
64
-
> You can share steps between test cases. For more information, see [Share steps](share-steps-between-test-cases.md).
53
+
4. Add test steps with a description of the action required to carry out the test and the expected results so that any team member can run the test. You can add attachments to a step if you want. Repeat until you add all the steps for the test.
65
54
66
55
A test case that you can run gets created.
67
-
68
-
You can also copy test cases. For more information, see [Copy or clone stories, issues and other work items](../boards/backlogs/copy-clone-work-items.md).
56
+
57
+
For more information, see[Share steps](share-steps-between-test-cases.md) and[Copy or clone stories, issues and other work items](../boards/backlogs/copy-clone-work-items.md).
69
58
70
59
## Assign configurations to test cases
71
60
72
61
You can specify configurations, such as different operating systems, web browsers, and other variations for your tests.
73
62
74
-
To assign test configurations to all test cases in a test suite, select the test suite, select **More options** or right-click to open the context menu, and then select **Assign configurations**.
75
-
76
-
In the **Assign configurations to test suite** dialog box, select the configurations you want.
63
+
1. Select the test suite > **More options** > **Assign configurations**, and in the dialog box, select your configurations.
77
64
78
65
79
66
80
-
You can also assign configurations to individual test cases. Select one or more test cases, select **More options**or right-click to open the context menu, and then select**Assign configuration**.
81
-
82
-
The **Assign configurations to selected test cases** dialog box opens. Make and save your changes.
67
+
You can also assign configurations to individual test cases. Select one or more test cases, select **More options**>**Assign configuration**.
68
+
69
+
1. Make your changes and then **Save**.
83
70
84
-
For more information about configurations, see [Test different configurations](test-different-configurations.md).
71
+
For more information, see [Test different configurations](test-different-configurations.md).
85
72
86
73
## Reorder test cases
87
74
88
75
You can reorder manual test cases in static suites, requirement-based suites, and query-based suites.
89
-
Open a test case, then use the up and down arrows to change the order.
90
76
91
-
77
+
Open a test case, and then use the up and down arrows to change the order.
92
78
93
-
There are also options to change order in the step context menu.
79
+
94
80
95
81
## Add existing test cases to a test suite
96
82
97
-
You can add existing test cases to a test suite.
83
+
Add existing test cases to a test suite with the following actions.
98
84
99
-
1. Select a test suite. From the **New Test Case** menu, select **Add existing test case**.
85
+
1. Select a test suite. From the **New Test Case** menu, select **Add existing test cases**.
100
86
101
87
102
88
103
-
1.In the **Add test cases to suite** dialog box, add search clauses, as needed, and then select **Run query**.
89
+
1. Add search clauses, as needed, and then select **Run query**.
104
90
105
91
106
92
107
-
1. After you find the test cases you want, select **Add test cases**.
93
+
2. When you find the test cases you want, highlight them and select **Add test cases**.
108
94
109
95
::: moniker-end
110
96
@@ -141,36 +127,33 @@ After reordering the tests, you can sort them by the **Order** field and then ru
141
127
::: moniker-end
142
128
143
129
> [!TIP]
144
-
> You can create a test case that automatically links to a requirement—User Story ([Agile](../boards/work-items/guidance/agile-process.md)), Product Backlog Item ([Scrum](../boards/work-items/guidance/scrum-process.md)), Requirement ([CMMI](../boards/work-items/guidance/cmmi-process.md)), or Issue ([Basic](../boards/get-started/plan-track-work.md))—when you create a test from the Kanban board. For more information, see [Add, run, and update inline tests](../boards/boards/add-run-update-tests.md).
145
-
>
130
+
> You can create a test case that automatically links to a requirement—User Story ([Agile](../boards/work-items/guidance/agile-process.md)), Product Backlog Item ([Scrum](../boards/work-items/guidance/scrum-process.md)), Requirement ([CMMI](../boards/work-items/guidance/cmmi-process.md)), or Issue ([Basic](../boards/get-started/plan-track-work.md))—when you create a test from the Kanban board. For more information, see [Add, run, and update inline tests](../boards/boards/add-run-update-tests.md).
146
131
147
132
## Use the Grid view to edit test cases
148
133
::: moniker range=">=azure-devops-2020"
149
134
150
-
You can copy and paste test cases into the **Grid** view.
135
+
Do the following steps to copy and paste test cases into the **Grid** view.
151
136
152
-
To open the **Grid** view, select the **Grid View** icon at the right.
137
+
1. Select the **GridView** icon.
153
138
154
-
139
+
155
140
156
-
Instead, you can select several test cases and open them for editing in the **Grid** view. In the context menu, select **Edit test case(s) in grid**.
141
+
2. Select one to several test cases, and then select **Edit test case(s) in grid**.
157
142
158
-
143
+
159
144
160
-
On the **Grid** context menu, you can add, delete, or clear rows.
145
+
3. Add, delete, or clear rows.
161
146
162
-
147
+
163
148
164
-
You can use the **Grid** view when you add multiple test cases to the test suite:
149
+
4. Optional. To add multiple test cases to the test suite, select **Add test cases using grid**.
165
150
166
-
151
+
152
+
- In the **List** view, use the column options to select the fields in the test case work item.
167
153
168
-
You can edit other fields in the **Grid** view.
169
-
In the **List** view, use the column options to select the fields in the test case work item.
170
-
171
-
154
+
172
155
173
-
You can then view and edit these fields when you switch to the **Grid** view.
156
+
View and edit these fields when you switch to the **Grid** view.
174
157
::: moniker-end
175
158
176
159
::: moniker range="<=azure-devops-2019"
@@ -188,7 +171,7 @@ You can use the **Grid View** when you add multiple test cases to the test suite
188
171
> [!NOTE]
189
172
> Do not use the Teams plugin for Excel to add or update test case work items.
190
173
> Excel cannot parse the format used to store test steps, and in some cases
191
-
> this may affect the formatting of the test case work items.
174
+
> this might affect the formatting of the test case work items.
192
175
193
176
You can edit other fields in the **Grid** view.
194
177
In the **List** view, use the column options to select the fields in the test case work item.
@@ -198,7 +181,7 @@ In the **List** view, use the column options to select the fields in the test ca
198
181
You can then view and edit these fields when you switch to the Grid view.
199
182
::: moniker-end
200
183
201
-
### Use Excel to copy test case information into a Grid view
184
+
### Use Excel to copy information into a Grid view
202
185
::: moniker range=">=azure-devops-2020"
203
186
You can copy test cases and test steps from an existing Excel worksheet.
204
187
Copy the columns from Excel that you want to use for the title, action, and expected results fields.
@@ -211,8 +194,8 @@ You can copy the data from the **Grid** view and paste it into your Excel worksh
211
194
Copying doesn't copy test step formatting, other than multiline, into the worksheet.
212
195
213
196
> [!NOTE]
214
-
> Do not use the Teams plugin for Excel to add or update test case work items.
215
-
> 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.
197
+
> Don't use the Teams plugin for Excel to add or update test case work items.
198
+
> Excel can't parse the format used to store test steps, and in some cases this may affect the formatting of the test case work items.
216
199
217
200
::: moniker-end
218
201
@@ -290,10 +273,11 @@ You can assign an individual test case to a tester.
290
273
::: moniker range=">=azure-devops-2020"
291
274
292
275
You can open a test case to view it or edit it.
293
-
To open a test case in a test suite, in the **Define** tab, double-select the name of the test case to open.
294
-
In the **Execute** tab, select a test case, open its context menu, and select **Edit test case**.
295
276
296
-
277
+
1. To open a test case in a test suite, in the **Define** tab, double-select the name of the test case to open.
278
+
2. In the **Execute** tab, select a test case, open its context menu, and select **Edit test case**.
279
+
280
+
297
281
298
282
A test case can be linked to test suites, requirements, and bugs.
299
283
To see linked items, in the **Define** tab, open the context menu for a test case, and select **View Linked Items**.
@@ -370,7 +354,7 @@ To manage or delete test artifacts, you must also have your access level set to
370
354
To delete test plans and test suites, you must be a member of the Project Administrators group or have the Area Path node-level [**Manage test plans** or **Manage test suites**](../organizations/security/set-permissions-access-work-tracking.md#manage-test-artifacts) permission set to **Allow**. To manage or delete test artifacts, you must also have your [access level](../organizations/security/access-levels.md) set to **Basic + Test Plans** or **Visual Studio Enterprise**. For more information, see [Delete test artifacts in Azure Boards](../boards/backlogs/delete-test-artifacts.md).
0 commit comments