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
To help avoid duplication, the Test & Feedback extension automatically
19
-
searches for and displays existing bugs, based on the keywords in the title,
20
-
as you file a new bug. You can choose to continue creating a new bug or add
21
-
your findings to an existing bug.
19
+
searches for and displays existing bugs, based on the keywords in the title as you file a new bug. You can choose to continue creating a new bug or add your findings to an existing bug.
1. As you type the title for a new bug, in the background the extension
26
-
searches for similar bugs that might be related to the issue you found
27
-
and displays a link to the results. Choose this link to see the results that have
28
-
similar title keywords.
23
+
## Add your findings to a bug
29
24
30
-
25
+
1. Enter the title for a bug.
26
+
27
+
In the background, the extension searches for similar bugs that might be related to the issue you found and displays a link to the results.
28
+
29
+
2. Select the link to see the results that have similar title keywords.
30
+
31
+
31
32
32
-
The form displays **0 Similar** if it doesn't find any matching bugs.
33
-
In this case, or if you don't see a "similar" link, you can create a
34
-
new bug containing your screenshots, notes, and videos
35
-
as described in [this article](connected-mode-exploratory-testing.md).
33
+
The form displays **0 Similar** if it doesn't find any matching bugs. In this case, or if you don't see a "similar" link, you can create a new bug that contains your screenshots, notes, and videos, as described in [Connected mode exploratory testing](connected-mode-exploratory-testing.md).
36
34
37
-
1. If you see a bug you want to update, instead of creating a new one:
35
+
3. To update a bug, do the following tasks, rather than create a new one.
38
36
39
-
-Select it in the list and choose**Edit**.
37
+
-Choose it from the list and select**Edit**.
40
38
41
-
39
+
42
40
43
-
- The extension appends all your screenshots, notes, and videos to
41
+
The extension appends all your screenshots, notes, and videos to
44
42
the existing bug.
45
43
46
44
- Save the updated bug.
47
45
48
-
49
-
50
-
1. If, instead, you decide not to update an existing bug, ignore the "similar" link and:
46
+
51
47
52
-
- Choose the **New bug** link to return to the bug details form.
48
+
4. OR, if you decide not to update an existing bug, ignore the "similar" link and select **New bug** to return to the bug details form.
53
49
54
-
50
+
55
51
56
-
- Enter the details for the new bug and save it
57
-
as described in [this article](connected-mode-exploratory-testing.md).<p />
52
+
- Enter the details for the new bug and save it, as described in [Connected mode exploratory testing](connected-mode-exploratory-testing.md).
58
53
59
-
1. Continue exploring your app, filing bugs and tasks, and creating test cases.
54
+
5. Continue to explore your app, file bugs and tasks, and create test cases.
60
55
61
56
## See your exploratory session results
62
57
63
58
After you file bugs, create tasks, or create test cases, they show up in the "Recent exploratory sessions" page in Azure Test Plans.
64
59
65
-
*See how you can [view your sessions and get insights](insights-exploratory-testing.md).
60
+
See how you can [view your sessions and get insights](insights-exploratory-testing.md).
66
61
67
-
## See Also
62
+
## Related articles
68
63
69
64
*[Use the Test & Feedback extension in Connected mode](connected-mode-exploratory-testing.md)
70
65
*[Explore work items with exploratory testing](explore-workitems-exploratory-testing.md)
Copy file name to clipboardExpand all lines: docs/test/associate-automated-test-with-test-case.md
+32-49
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Continuous testing. Associate an automated test with a test case us
4
4
ms.assetid: 606679F2-1604-40EA-A720-63CDDA93DD76
5
5
ms.service: azure-devops-test-plans
6
6
ms.custom: UpdateFrequency3
7
-
ms.topic: conceptual
7
+
ms.topic: how-to
8
8
ms.author: rbatra
9
9
author: rohit-batra
10
10
ms.date: 12/07/2018
@@ -21,98 +21,80 @@ Consider using Visual Studio to associate automated tests with a test case when:
21
21
* You created a manual test case that you later decide is a good test
22
22
to automate, but you still want to be able to run that test as part of a test plan.
23
23
Tests can be run in the CI/CD pipeline by choosing the test plan or test suite
24
-
in the settings of the [Visual Studio Test](/azure/devops/pipelines/tasks/reference/vstest-v2) task.
25
-
Automated tests can also be run from the **Test Plans** web portal.
26
-
If you're using XAML builds you can also
27
-
[run these automated tests by using Microsoft Test Manager](/previous-versions/azure/devops/test/mtm/run-automated-tests-with-microsoft-test-manager).
28
-
24
+
in the settings of the [Visual Studio Test](/azure/devops/pipelines/tasks/reference/vstest-v2) task. Automated tests can also be run from the **Test Plans** web portal.
25
+
If you're using XAML builds, you can also [run these automated tests by using Microsoft Test Manager](/previous-versions/azure/devops/test/mtm/run-automated-tests-with-microsoft-test-manager).
29
26
* You want to enable end-to-end traceability of requirements.
30
27
If your test cases are linked to requirements or user stories,
31
28
the results of the test execution can be used to establish the quality of those requirements.
32
29
33
-
The process to associate an automated test with a test case is:
30
+
## Create a test project and build pipeline
34
31
35
-
1. Create a test project containing your automated test.
36
-
[What types of tests are supported?](#test-types)
32
+
Do the following steps to create a test project and build pipeline.
37
33
34
+
1. Create a test project containing your automated test. [What types of tests are supported?](#test-types)
38
35
1. Check your test project into an Azure DevOps.
39
-
40
-
1. Create a build pipeline for your project, ensuring that it
41
-
contains the automated test.
36
+
1. Create a build pipeline for your project and ensure that it contains the automated test.
42
37
[What are the differences if I'm still using a XAML build?](#xaml-build)
43
38
44
-
1. Use Visual Studio Enterprise or Professional 2017 or a later version to associate the automated
45
-
test with a test case as shown [later in this article](#add-test). The test case were added to a test plan that uses the build you defined.
46
-
47
-
If you're using the build and release services in
48
-
Azure DevOps (not a [XAML build](#xaml-build)), you can run associated tests in the
49
-
build and release pipelines by using the
50
-
[Visual Studio Test](/azure/devops/pipelines/tasks/reference/vstest-v2) task.
51
-
You _can't_ run tests on-demand using Microsoft Test Manager unless you're using a XAML build.
52
-
53
-
The parameters in a test case aren't used by any automated test that
54
-
you associate with a test case. Iterations of a test case that use these
55
-
parameters are for manual tests only.
56
-
57
-
> For more information about checking in your test project and team build, see
58
-
[Add files to the server](../repos/tfvc/add-files-server.md)
59
-
and [Continuous integration on any platform](../pipelines/get-started/what-is-azure-pipelines.md).
60
-
For more information about action recordings and coded UI tests, see
61
-
[Recording and Playing Back Manual Tests](/previous-versions/azure/devops/test/mtm/record-play-back-manual-tests)
62
-
and [Use UI Automation To Test Your Code](/visualstudio/test/use-ui-automation-to-test-your-code).
63
-
64
39
<aname="add-test"></a>
40
+
65
41
## Associate your test
66
42
67
43
1. Open your solution in Visual Studio Enterprise or Professional 2017 or a later version.
68
-
69
44
2. If you don't know the identifier of the work item for the test case,
70
45
locate the test case in **Azure Test Plans** , or [query for the work item](../boards/queries/using-queries.md) in the **Work** hub.
71
-
72
46
3. When you know the identifier of the work item for the test case:
73
47
74
-
**If you are using Visual Studio 2017 or later version**, follow these steps to associate your tests.
48
+
**If you are using Visual Studio 2017 or later version**, do the following steps to associate your tests.
75
49
76
50
- If the **Test Explorer** window isn't displayed, open it from the **Test | Windows** menu.
77
-
78
51
- If your tests aren't displayed in **Test Explorer**, build the solution.
79
-
80
52
- In **Test Explorer**, select the test method you want to associate and choose **Associate to Test Case**.
81
-
82
53
- In the dialog that opens, type the test case identifier and choose **Add Association**, then choose **Save**.
83
54
84
-
55
+
85
56
86
-
> The dialog shows a list of test cases currently associated with the selected test method.
87
-
You cannot associate more than one test method with a test case, but you can associate a
57
+
The dialog shows a list of test cases currently associated with the selected test method.
58
+
You can't associate more than one test method with a test case, but you can associate a
88
59
test method with more than one test case.
89
60
61
+
If you're using the build and release services in Azure DevOps, not a [XAML build](#xaml-build), you can run associated tests in the build and release pipelines by using the[Visual Studio Test](/azure/devops/pipelines/tasks/reference/vstest-v2) task. You _can't_ run tests on-demand using Microsoft Test Manager unless you're using a XAML build.
62
+
63
+
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.
64
+
65
+
For more information, see the following articles:
66
+
-[Add files to the server](../repos/tfvc/add-files-server.md)
67
+
-[Continuous integration on any platform](../pipelines/get-started/what-is-azure-pipelines.md)
68
+
-[Recording and Playing Back Manual Tests](/previous-versions/azure/devops/test/mtm/record-play-back-manual-tests)
69
+
-[Use UI Automation To Test Your Code](/visualstudio/test/use-ui-automation-to-test-your-code)
70
+
90
71
<aname="test-plan"></a>
91
72
92
73
## FAQs
93
74
94
75
See the following frequently asked questions (FAQs).
95
76
96
77
<aname="test-types"></a>
78
+
97
79
### Q: What types of tests are supported?
98
80
99
-
**A**: The following limitations exist for each test type:
81
+
**A**: The following capabilities and limitations exist for each test type:
100
82
101
-
* Coded UI test, Selenium tests, and unit tests written using
102
-
Version 1 of the MSTest framework **can** be associated with a test case.
83
+
* Coded UI test, Selenium tests, and unit tests written using Version 1 of the MSTest framework **can** be associated with a test case.
103
84
* Tests that use MSTest v2, NUnit, and xUnit frameworks **can** be associated
104
85
with a test case work item when using Visual Studio 15.9 Preview 2 or later.
105
86
However, these tests can't be run using Microsoft Test Manager and XAML builds.
106
87
* Tests that use the .NET core framework **can** be associated with a test case
107
88
work item when using Visual Studio 15.9 Preview 2 or later.
108
-
To run the .NET core tests the appropriate target framework must be specified
109
-
in a [runsettings file](/visualstudio/test/configure-unit-tests-by-using-a-dot-runsettings-file).
89
+
Run the .NET core tests. The appropriate target framework must be specified
90
+
in a [runsettings file](/visualstudio/test-configure-unit-tests-by-using-a-dot-runsettings-file).
110
91
However, these tests can't be run using Microsoft Test Manager and XAML builds.
111
92
* Tests that use other test frameworks such as Chutzpah (for JavaScript tests
112
93
such as Mocha or QUnit), or Jest **cannot** be associated with a test case.
113
94
* Associating generic tests **may** work, but running these tests isn't supported.
114
95
115
96
<aname="xaml-build"></a>
97
+
116
98
### Q: What are the differences if I'm still using a XAML build?
117
99
118
100
**A**: If you're using a XAML build in Azure Pipelines, you can run tests
@@ -122,15 +104,16 @@ You can also run tests using Microsoft Test Manager and a
@@ -22,11 +22,11 @@ For an overview of test objects and terminology, see [Test objects and terms](te
22
22
23
23
## Export test cases
24
24
25
-
1. From the **Test Plans>Test plans** page, choose the test plan with the test suite containing the test cases you want to export.
25
+
1. From the **Test Plans** > **Test plans** page, choose the test plan with the test suite containing the test cases you want to export.
26
26
27
-
2. Optional. Choose :::image type="icon" source="media/icons/column-options.png"::: **Column options** to add fields to include in the download file.
27
+
2.(Optional) Select :::image type="icon" source="media/icons/column-options.png"::: **Column options** to add fields to include in the download file.
28
28
29
-
3. To export all test cases for the test suite, choose from**Export test cases to CSV** or **Export test cases to XLSX**.
29
+
3. To export all test cases for the test suite, select either**Export test cases to CSV** or **Export test cases to XLSX**.
30
30
31
31
:::image type="content" source="media/bulk-import-test-case/export-test-cases-test-suite.png" alt-text="Screenshot of Export test cases from the selected test suite.":::
32
32
@@ -42,14 +42,12 @@ For an overview of test objects and terminology, see [Test objects and terms](te
42
42
43
43
:::image type="content" source="media/bulk-import-test-case/choose-import-test-cases.png" alt-text="Screenshot of Import test cases to the selected test suite.":::
44
44
45
-
46
45
2. Choose the file to import from the dialog that opens, and then choose **Import**.
47
46
48
47
:::image type="content" source="media/bulk-import-test-case/import-test-cases-dialog.png" alt-text="Screenshot of Import Test Cases dialog.":::
49
48
50
49
3. Choose **Confirm** in the **Confirm import** dialog that displays. If you specify test cases that are already defined in the test suite, some elements might get over written during import.
51
50
52
-
53
51
<aid="import-test-cases"></a>
54
52
55
53
## Update existing test cases
@@ -126,12 +124,11 @@ A: Ensure to follow the below limitations:
126
124
* The user performing the import must have permissions on the area and iteration paths for test plan and test suite they're planning to import or export.
127
125
* Copy and Import operations fail if the related link count exceeds 1000 for the test case.
128
126
129
-
## Next step
127
+
## Next steps
130
128
131
129
> [!div class="nextstepaction"]
132
130
> [Run manual tests](run-manual-tests.md)
133
131
134
-
135
132
## Related articles
136
133
137
134
-[Create test plans and test suites](create-a-test-plan.md)
@@ -142,4 +139,3 @@ A: Ensure to follow the below limitations:
142
139
-[Test objects and terms](test-objects-overview.md)
143
140
-[Create a query based on build and test integration fields](../boards/queries/build-test-integration.md)
144
141
-[Customize and manage the test experience](/previous-versions/azure/devops/reference/witadmin/tcm-customize-manage-test-experience)
0 commit comments