Merge pull request #9091 from MicrosoftDocs/users/chcomley/test-objects-overview

Test Plans - Rework test objects overview, Manual test permissions, and prerequisites

Author: v-regandowner

docs/test/includes/prerequisites-stakeholder.md

@@ -11,4 +11,4 @@ ms.date: 01/13/2025
 |--------------|-------------|
 | **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
 | **Access levels** | To request or provide feedback: At least **Stakeholder** access. |
-| **Permissions** | - To add or modify bugs or other work item types: **Edit work items in this node** permission set to **Allow** under the corresponding **Area Path**. <br> - To add new tags: **Create tag definition** permission set to **Allow**. <br> For more information, see [Set permissions and access for testing](../../organizations/security/set-permissions-access-test.md). |
+| **Permissions** | - To add or modify bugs or other work item types: **Edit work items in this node** permission set to **Allow** under the corresponding **Area Path**. <br> - To add new tags: **Create tag definition** permission set to **Allow**. <br> For more information, see [Manual test access and permissions](../manual-test-permissions.md). |

docs/test/includes/prerequisites.md

@@ -11,7 +11,7 @@ ms.date: 01/13/2025
 |--------------|-------------|
 | **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
 | **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. <br>- To exercise the full range of test-related features: [Basic + Test Plans](../../organizations/billing/buy-access-tfs-test-hub.md) access level or one of the following subscriptions: <br> - [Enterprise](https://visualstudio.microsoft.com/vs/enterprise/) <br>- [Test Professional](https://visualstudio.microsoft.com/vs/test-professional/) <br>- [MSDN Platforms](https://visualstudio.microsoft.com/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**. <br>- To modify test plan properties such as build and test settings: **Manage test plans** permission set to **Allow** under the corresponding **Area Path**. <br>- 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**. <br>- Project-level permissions that you might need include: <br>- To view, create, or delete test runs: **View test runs**, **Create test runs**, and **Delete test runs** permission set to **Allow**. <br> - To manage test configurations or test environments: **Manage test configurations** and **Manage test environments**. <br>- To add new tags to test-based work items: **Create tag definition** permission set to **Allow**. <br>- To move test-based work items out of a project: **Move work items out of this project** permission set to **Allow**. <br>- To delete or restore test-based work items: **Delete and restore work items** permission set to **Allow**. <br>- To permanently delete test-based work items: **Permanently delete work items** permission set to **Allow**. |
+| **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**. <br>- To modify test plan properties such as build and test settings: **Manage test plans** permission set to **Allow** under the corresponding **Area Path**. <br>- 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**. <br>- Project-level permissions that you might need include: <br>- To view, create, or delete test runs: **View test runs**, **Create test runs**, and **Delete test runs** permission set to **Allow**. <br> - To manage test configurations or test environments: **Manage test configurations** and **Manage test environments**. <br>- To add new tags to test-based work items: **Create tag definition** permission set to **Allow**. <br>- To move test-based work items out of a project: **Move work items out of this project** permission set to **Allow**. <br>- To permanently delete test-based work items: **Permanently delete work items** permission set to **Allow**. |
 
 For more information, see [Manual test access and permissions](../manual-test-permissions.md).
 

docs/test/manual-test-permissions.md

@@ -1,69 +1,83 @@
 ---
 title: Permissions, licensing, and access for manual testing
-description: Default permissions and access levels in Azure DevOps for manual and exploratory testing and problems.
+description: Default permissions and access levels in Azure DevOps for manual and exploratory testing.
 ms.assetid: 91146CFD-A4CE-4CC5-973D-1633419CAFDE
 ms.service: azure-devops-test-plans
 ms.custom: UpdateFrequency3
 ms.topic: reference
 ms.author: pliaros
 author: rohit-batra
 monikerRange: '<= azure-devops'
-ms.date: 09/15/2021
+ms.date: 04/01/2026
 ms.update-cycle: 1095-days
 ---
 
 # Manual test access and permissions 
 
 [!INCLUDE [version-lt-eq-azure-devops](../includes/version-lt-eq-azure-devops.md)]
 
-Access levels and permissions control access to Azure Test Plans features. 
+This article covers the access levels, licensing, and permissions required for manual and exploratory testing in Azure Test Plans.
 
-## Prerequisites
+## Access and licensing 
+
+To use the full range of Test Plans features, you need [Basic + Test Plans](../organizations/billing/buy-access-tfs-test-hub.md) access level or one of the following Visual Studio subscriptions, which include Test Plans at no extra charge:
+
+- [Visual Studio Enterprise](https://visualstudio.microsoft.com/vs/enterprise/)
+- [Visual Studio Test Professional](https://visualstudio.microsoft.com/vs/test-professional/)
+- [MSDN Platforms](https://visualstudio.microsoft.com/msdn-platforms/)
 
-| Category | Requirement |
-|--------------|-------------|
-| **Project access** | [Project member](../organizations/security/add-users-team-project.md). |
-| **Access levels** |- To access the Test Plans web portal: At least **Basic** access.<br>- To define and manage test plans, test suites, and test cases: **Basic + Test Plans** access.|
+Users without one of these subscriptions must purchase **Basic + Test Plans** access. For more information, see [Compare Visual Studio subscriptions](https://www.visualstudio.com/vs/pricing).
 
 > [!NOTE]  
-> Users granted **Stakeholder** access have no access to features or functions supported through the Test Plans or Test web portal. However, they can provide feedback through the **Test & Feedback** extension. For more information, see [Stakeholder access quick reference](../organizations/security/stakeholder-access.md).
+> Users with **Stakeholder** access can't access the Test Plans web portal. However, they can provide feedback through the Test & Feedback extension. For more information, see [Stakeholder access quick reference](../organizations/security/stakeholder-access.md).
+
+The following table summarizes the access level required for each task. 
+
+| Task | Access level |
+|---|---|
+| Provide feedback using the Test & Feedback extension. | **Stakeholder** | 
+| Execute tests, mark test outcomes. | **Basic** |
+| Chart test status, view reports. | **Basic** |
+| Create and manage test plans and test suites. | **Basic + Test Plans** |
+| Author test cases using a grid-like view and edit in Test Runner. | **Basic + Test Plans** |
+| Assign test cases to suites, move test cases, and order test cases. | **Basic + Test Plans** |
+| Prepare for execution such as assigning configurations or testers. | **Basic + Test Plans** | 
+| Create and manage configurations and parameters. | **Basic + Test Plans** | 
+| Prepare User Acceptance Testing. | **Basic + Test Plans** |
 
-## Access and licensing 
+<a id="access-by-user-role"></a>
 
-To exercise the full range of test-related features, have [Basic + Test Plans](../organizations/billing/buy-access-tfs-test-hub.md) access level or have one of the following subscriptions:
-	- [Visual Studio Enterprise](https://visualstudio.microsoft.com/vs/enterprise/)
-	- [Visual Studio Test Professional](https://visualstudio.microsoft.com/vs/test-professional/)
-	- [MSDN Platform](https://visualstudio.microsoft.com/msdn-platforms/)
+## Permissions
 
-Users who have one of the above subscriptions can exercise all Test Plans features for no extra charge. For more information, see [Compare Visual Studio subscriptions](https://www.visualstudio.com/vs/pricing).
- 
-Nonsubscribers must purchase **Basic + Test Plans** to use Test Plans, which can be for any specified number of users.
+In addition to the required access level, you need specific permissions for certain tasks. Because manual testing is managed through [test-specific work item types](test-objects-overview.md), test artifacts are subject to the same permissions that manage work items.
 
-> [!IMPORTANT]  
-> Manual testers can execute tests with **Basic** access. Licenses for this extension also give users rights to use [Microsoft Test Manager](/previous-versions/azure/devops/test/mtm/guidance-mtm-usage) (a deprecated on-premises client).
+The following table lists permissions that control test-related tasks, organized by level.
 
-The following table summarizes the license requirements required to exercise select tasks. 
+### Project-level permissions
 
-| Task  | Access level|
-| --- | --- |
-| Provide feedback | Stakeholder | 
-| Execute tests, Mark test outcomes | Basic |
-| Chart tasks, View reports | Basic |
-| Create and manage test plans and test suites | Basic + Test Plans  |
-| Author test cases using a grid-like view and edit in the Test Runner | Basic + Test Plans  |
-| Assign test cases to suites, move test cases, and order test cases | Basic + Test Plans  |
-| Prepare for execution such as assigning configurations or testers | Basic + Test Plans  | 
-| Create and manage configurations and parameters | Basic + Test Plans  | 
-| Prepare User Acceptance Testing | Basic + Test Plans  |
+| Task | Permission |
+|---|---|
+| View test runs. | **View test runs** |
+| Create test runs. | **Create test runs** |
+| Delete test runs. | **Delete test runs** |
+| Add or edit test configurations and variables. | **Manage test configurations** |
+| Create and delete test environments. This permission is used with the [`tcm testenvironments`](test-case-managment-reference.md) CLI and has no corresponding option in the Test Plans web portal. | **Manage test environments** |
+| Add new tags to test-based work items. | **Create tag definition** |
+| Permanently delete test-specific work items. | **Permanently delete work items** |
 
-<a id="access-by-user-role"></a>
+### Area Path permissions
 
-## Permissions
+| Task | Permission |
+|---|---|
+| View test plans, test suites, test cases, and other test-based work items. | **View work items in this node** |
+| Add or modify test plans, test suites, test cases, and other test-based work items. | **Edit work items in this node** |
+| Modify test plan properties such as test run and test outcome settings. | **Manage test plans** |
+| Create and delete test suites. Add and remove test cases from test suites. Change test configurations associated with test suites. Modify a test suite hierarchy (move a test suite). | **Manage test suites** |
 
-In addition to having the necessary access level, you also need the necessary permissions to exercise select tasks. Because manual testing is managed through [test-specific work item types](test-objects-overview.md), they're subject to some of the same permissions that manage work items.  
 
-The following table provides the default permissions assigned to the built-in security groups: **Readers**, **Contributors**, and **Project Administrators**. Permissions are assigned for Area Paths and at the project-level. To learn how, see [Set permissions and access for testing](../organizations/security/set-permissions-access-test.md). 
+### Default permissions by security group
 
+The following table provides the default permissions assigned to the built-in security groups: **Readers**, **Contributors**, and **Project Administrators**. To learn how to change these settings, see [Set permissions and access for testing](../organizations/security/set-permissions-access-test.md). 
 
 [!INCLUDE [test](../organizations/security/includes/test.md)]