Add findings to existing bugs with exploratory testing
Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019
To help avoid duplication, the Test & Feedback extension automatically 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.
Prerequisites
| Category | Requirement |
|---|---|
| Project access | Project member. |
| Access levels | - To view test-related work items or run test cases: At least Basic access. Users with Stakeholder access have no access to Test Plans. - To exercise the full range of test-related features: Basic + Test Plans access level or one of the following subscriptions: - Enterprise - Test Professional - MSDN Platforms |
| Permissions | - To add or modify test plans, test suites, test cases, or other test-based work item types: Edit work items in this node permission set to Allow under the corresponding Area Path. - To modify test plan properties such as build and test settings: Manage test plans permission set to Allow under the corresponding Area Path. - To create and delete test suites, add and remove test cases from test suites, or change test configurations associated with test suites: Manage test suites permission set to Allow under the corresponding Area Path. - Project-level permissions that you might need include: - To view, create, or delete test runs: View test runs, Create test runs, and Delete test runs permission set to Allow. - To manage test configurations or test environments: Manage test configurations and Manage test environments. - To add new tags to test-based work items: Create tag definition permission set to Allow. - To move test-based work items out of a project: Move work items out of this project permission set to Allow. - To delete or restore test-based work items: Delete and restore work items permission set to Allow. - To permanently delete test-based work items: Permanently delete work items permission set to Allow. |
For more information, see Manual test access and permissions.
Add your findings to a bug
Enter the title for a bug.
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.
Select the link to see the results that have similar title keywords.
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.
To update a bug, do the following tasks, rather than create a new one.
Choose it from the list and select Edit.
The extension appends all your screenshots, notes, and videos to the existing bug.
Save the updated bug.
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.
- Enter the details for the new bug and save it, as described in Connected mode exploratory testing.
Continue to explore your app, file bugs and tasks, and create test cases.
See your exploratory session results
After you file bugs, create tasks, or create test cases, they show up in the "Recent exploratory sessions" page in Azure Test Plans.
See how you can view your sessions and get insights.