diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index d7db7cd9638..49a97c9bb1a 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -18229,6 +18229,11 @@
"source_path": "docs/pipelines/apps/cd/azure/build-azure-vm-template.md",
"redirect_url": "/azure/devops/pipelines/apps/cd/azure/deploy-arm-template",
"redirect_document_id": false
+ },
+ {
+ "source_path": "docs/test/new-test-plans-page.md",
+ "redirect_url": "/azure/devops/test/navigate-test-plans",
+ "redirect_document_id": false
}
]
}
diff --git a/docs/organizations/settings/work/object-limits.md b/docs/organizations/settings/work/object-limits.md
index 168da4d2925..0cb83e6cd6f 100644
--- a/docs/organizations/settings/work/object-limits.md
+++ b/docs/organizations/settings/work/object-limits.md
@@ -8,13 +8,13 @@ ms.assetid: E5FABB7C-ECA8-4FA5-9488-4AD78C60869A
ms.author: kaelli
author: KathrynEE
ms.topic: reference
-monikerRange: ">= tfs-2013"
+monikerRange: "<= azure-devops"
ms.date: 06/09/2021
---
# Work tracking, process, and project limits
-[!INCLUDE [temp](../../../includes/version-tfs-all-versions.md)]
+[!INCLUDE [temp](../../../includes/version-vsts-tfs-all-versions.md)]
This article defines operational and object limits placed on work tracking operations and work tracking customization. In addition to the specified hard limits on select objects, certain practical limits apply. When you customize work item types (WITs), consider the limits placed on objects.
diff --git a/docs/project/navigation/preview-features.md b/docs/project/navigation/preview-features.md
index 254947a8655..2f706ec9127 100644
--- a/docs/project/navigation/preview-features.md
+++ b/docs/project/navigation/preview-features.md
@@ -60,7 +60,7 @@ The follow table indicates which preview features can be enabled per user or tea
[Copy Dashboard Experience](../../report/dashboards/copy-dashboard.md)
[Experimental themes](#experimental-themes)
[Full Access to Azure Pipelines for Stakeholders](../../organizations/security/provide-stakeholder-pipeline-access.md)
- [Historical graph for agent pools](/azure/devops/release-notes/2020/sprint-179-update#historical-graph-for-agent-pools-preview)
+ [Historical graph for agent pools](../../pipelines/agents/pool-consumption-report.md)
:::column-end:::
:::column span=".5":::
✔️
@@ -332,7 +332,7 @@ With **Experimental themes** enabled, you can select among a number of additiona
### Azure Test Plans
-- [New Test Plans Page](../../test/new-test-plans-page.md)
+- [New Test Plans Page](../../test/navigate-test-plans.md)
- [New Test Plan Experience](/azure/devops/release-notes/2018/jun-19-vsts#test-1)
### Dashboards and Analytics
diff --git a/docs/repos/git/pull-requests.md b/docs/repos/git/pull-requests.md
index 3805d916471..2e4c5a35748 100644
--- a/docs/repos/git/pull-requests.md
+++ b/docs/repos/git/pull-requests.md
@@ -199,13 +199,16 @@ Initiate pull requests directly from Visual Studio.

+::: moniker range=">=azure-devops-2020"
+
### From the Azure DevOps Services CLI
-You can now manage your pull requests and other resources from the command line with [azure-devops](/cli/azure/?view=azure-cli-latest&preserve-view=true). Azure Repos and Azure DevOps Server, formerly Team Foundation Server 2017 Update 2 or later, support pull requests by using the command line.
+You can manage your pull requests and other resources from the command line with [azure-devops](/cli/azure/?view=azure-cli-latest&preserve-view=true). Azure Repos and Azure DevOps Server.
+
+For more information about working with the Azure DevOps Services CLI, see [Get started with CLI](../../cli/index.md).
-For a list of commands to create and manage pull requests, see [Manage pull requests](/cli/vsts/code/pr).
+::: moniker-end
-For more information about working with the Azure DevOps Services CLI, see [Get started with CLI](/cli/vsts/get-started).
diff --git a/docs/test/includes/prerequisites.md b/docs/test/includes/prerequisites.md
new file mode 100644
index 00000000000..0fa8f0edb1b
--- /dev/null
+++ b/docs/test/includes/prerequisites.md
@@ -0,0 +1,19 @@
+---
+ms.technology: devops-test
+ms.author: kaelli
+author: KathrynEE
+ms.topic: include
+ms.date: 07/09/2020
+---
+
+
+## Prerequisites
+
+- To use Test Plans, you must have been granted [Basic + Test Plans](https://marketplace.visualstudio.com/items?itemName=ms.vss-testmanager-web) access level or have one of the following subscriptions:
+
+ - [Enterprise](https://visualstudio.microsoft.com/vs/enterprise/)
+ - [Test Professional](https://visualstudio.microsoft.com/vs/test-professional/)
+ - [MSDN Platforms](https://visualstudio.microsoft.com/msdn-platforms/)
+
+- To create, delete, or manage test plans, test suites, test environments, or other test artifacts, you must have the required permissions. Members of the Contributors group are granted these permissions by default. For specific permission settings, see [Manual testing permissions and access](../manual-test-permissions.md).
+
\ No newline at end of file
diff --git a/docs/test/index.yml b/docs/test/index.yml
index 0b7f1f9d495..d90efb3d182 100644
--- a/docs/test/index.yml
+++ b/docs/test/index.yml
@@ -26,6 +26,8 @@ landingContent:
links:
- text: What is Azure Test Plans?
url: ../test/overview.md
+ - text: Navigate Test Plans
+ url: ../test/navigate-test-plans.md
- linkListType: video
links:
- text: Capturing actionable feedback with manual testing
diff --git a/docs/test/media/navigate/add-test-cases-to-suite-dialog.png b/docs/test/media/navigate/add-test-cases-to-suite-dialog.png
new file mode 100644
index 00000000000..547bec2f02d
Binary files /dev/null and b/docs/test/media/navigate/add-test-cases-to-suite-dialog.png differ
diff --git a/docs/test/media/navigate/all-test-plans-icon.png b/docs/test/media/navigate/all-test-plans-icon.png
new file mode 100644
index 00000000000..38db5bad4df
Binary files /dev/null and b/docs/test/media/navigate/all-test-plans-icon.png differ
diff --git a/docs/test/media/navigate/bulk-save-icon.png b/docs/test/media/navigate/bulk-save-icon.png
new file mode 100644
index 00000000000..997e2edce57
Binary files /dev/null and b/docs/test/media/navigate/bulk-save-icon.png differ
diff --git a/docs/test/media/navigate/column-options-icon.png b/docs/test/media/navigate/column-options-icon.png
new file mode 100644
index 00000000000..4f0b47bc32a
Binary files /dev/null and b/docs/test/media/navigate/column-options-icon.png differ
diff --git a/docs/test/media/navigate/column-options.png b/docs/test/media/navigate/column-options.png
new file mode 100644
index 00000000000..a1a2fdf7f39
Binary files /dev/null and b/docs/test/media/navigate/column-options.png differ
diff --git a/docs/test/media/navigate/copy-test-cases.png b/docs/test/media/navigate/copy-test-cases.png
new file mode 100644
index 00000000000..dfe1149eef3
Binary files /dev/null and b/docs/test/media/navigate/copy-test-cases.png differ
diff --git a/docs/test/media/new-test-plans-page/copy-test-plan-dialog.png b/docs/test/media/navigate/copy-test-plan-dialog.png
similarity index 100%
rename from docs/test/media/new-test-plans-page/copy-test-plan-dialog.png
rename to docs/test/media/navigate/copy-test-plan-dialog.png
diff --git a/docs/test/media/navigate/copy-test-plan.png b/docs/test/media/navigate/copy-test-plan.png
new file mode 100644
index 00000000000..6e875d82566
Binary files /dev/null and b/docs/test/media/navigate/copy-test-plan.png differ
diff --git a/docs/test/media/navigate/define-tab-context-menu.png b/docs/test/media/navigate/define-tab-context-menu.png
new file mode 100644
index 00000000000..e8e29d26ce1
Binary files /dev/null and b/docs/test/media/navigate/define-tab-context-menu.png differ
diff --git a/docs/test/media/navigate/define-tab-tasks.png b/docs/test/media/navigate/define-tab-tasks.png
new file mode 100644
index 00000000000..fa5a984cb5e
Binary files /dev/null and b/docs/test/media/navigate/define-tab-tasks.png differ
diff --git a/docs/test/media/navigate/define-tab-toolbar-2.png b/docs/test/media/navigate/define-tab-toolbar-2.png
new file mode 100644
index 00000000000..9779f1d6313
Binary files /dev/null and b/docs/test/media/navigate/define-tab-toolbar-2.png differ
diff --git a/docs/test/media/new-test-plans-page/enable-preview-feature.png b/docs/test/media/navigate/enable-preview-feature.png
similarity index 100%
rename from docs/test/media/new-test-plans-page/enable-preview-feature.png
rename to docs/test/media/navigate/enable-preview-feature.png
diff --git a/docs/test/media/new-test-plans-page/execute-tab-execution-history.png b/docs/test/media/navigate/execute-tab-execution-history.png
similarity index 100%
rename from docs/test/media/new-test-plans-page/execute-tab-execution-history.png
rename to docs/test/media/navigate/execute-tab-execution-history.png
diff --git a/docs/test/media/navigate/execute-tab-test-points-overview.png b/docs/test/media/navigate/execute-tab-test-points-overview.png
new file mode 100644
index 00000000000..4ef5ada238a
Binary files /dev/null and b/docs/test/media/navigate/execute-tab-test-points-overview.png differ
diff --git a/docs/test/media/navigate/expand-collapse-icons.png b/docs/test/media/navigate/expand-collapse-icons.png
new file mode 100644
index 00000000000..ebe6a05fed4
Binary files /dev/null and b/docs/test/media/navigate/expand-collapse-icons.png differ
diff --git a/docs/test/media/navigate/export-dialog.png b/docs/test/media/navigate/export-dialog.png
new file mode 100644
index 00000000000..625cdb86bda
Binary files /dev/null and b/docs/test/media/navigate/export-dialog.png differ
diff --git a/docs/test/media/navigate/filter-icon.png b/docs/test/media/navigate/filter-icon.png
new file mode 100644
index 00000000000..5db588cd004
Binary files /dev/null and b/docs/test/media/navigate/filter-icon.png differ
diff --git a/docs/test/media/navigate/grid-icon.png b/docs/test/media/navigate/grid-icon.png
new file mode 100644
index 00000000000..438b220aebe
Binary files /dev/null and b/docs/test/media/navigate/grid-icon.png differ
diff --git a/docs/test/media/navigate/grid-refresh.png b/docs/test/media/navigate/grid-refresh.png
new file mode 100644
index 00000000000..99d6815b1d8
Binary files /dev/null and b/docs/test/media/navigate/grid-refresh.png differ
diff --git a/docs/test/media/navigate/grid-view-cell-options.png b/docs/test/media/navigate/grid-view-cell-options.png
new file mode 100644
index 00000000000..1c441208739
Binary files /dev/null and b/docs/test/media/navigate/grid-view-cell-options.png differ
diff --git a/docs/test/media/navigate/grid-view.png b/docs/test/media/navigate/grid-view.png
new file mode 100644
index 00000000000..50d16a893a1
Binary files /dev/null and b/docs/test/media/navigate/grid-view.png differ
diff --git a/docs/test/media/navigate/import-test-suites-dialog.png b/docs/test/media/navigate/import-test-suites-dialog.png
new file mode 100644
index 00000000000..a989b1c7801
Binary files /dev/null and b/docs/test/media/navigate/import-test-suites-dialog.png differ
diff --git a/docs/test/media/navigate/linked-items-dialog.png b/docs/test/media/navigate/linked-items-dialog.png
new file mode 100644
index 00000000000..a0131133cd7
Binary files /dev/null and b/docs/test/media/navigate/linked-items-dialog.png differ
diff --git a/docs/test/media/new-test-plans-page/new-test-plans-page.png b/docs/test/media/navigate/new-test-plans-page.png
similarity index 100%
rename from docs/test/media/new-test-plans-page/new-test-plans-page.png
rename to docs/test/media/navigate/new-test-plans-page.png
diff --git a/docs/test/media/navigate/show-test-points-from-child-nodes-icon.png b/docs/test/media/navigate/show-test-points-from-child-nodes-icon.png
new file mode 100644
index 00000000000..abe36eebb46
Binary files /dev/null and b/docs/test/media/navigate/show-test-points-from-child-nodes-icon.png differ
diff --git a/docs/test/media/navigate/test-plan-header.png b/docs/test/media/navigate/test-plan-header.png
new file mode 100644
index 00000000000..77af1ba80e6
Binary files /dev/null and b/docs/test/media/navigate/test-plan-header.png differ
diff --git a/docs/test/media/navigate/test-plan-overview-1.png b/docs/test/media/navigate/test-plan-overview-1.png
new file mode 100644
index 00000000000..ef5a9b90a0e
Binary files /dev/null and b/docs/test/media/navigate/test-plan-overview-1.png differ
diff --git a/docs/test/media/navigate/test-plan-overview-2.png b/docs/test/media/navigate/test-plan-overview-2.png
new file mode 100644
index 00000000000..e3d1a33bc22
Binary files /dev/null and b/docs/test/media/navigate/test-plan-overview-2.png differ
diff --git a/docs/test/media/new-test-plans-page/test-plan-overview.png b/docs/test/media/navigate/test-plan-overview.png
similarity index 100%
rename from docs/test/media/new-test-plans-page/test-plan-overview.png
rename to docs/test/media/navigate/test-plan-overview.png
diff --git a/docs/test/media/navigate/test-plan-settings-dialog-undefined.png b/docs/test/media/navigate/test-plan-settings-dialog-undefined.png
new file mode 100644
index 00000000000..ecb0c505f9d
Binary files /dev/null and b/docs/test/media/navigate/test-plan-settings-dialog-undefined.png differ
diff --git a/docs/test/media/new-test-plans-page/test-plans-placeholder.png b/docs/test/media/navigate/test-plans-placeholder.png
similarity index 100%
rename from docs/test/media/new-test-plans-page/test-plans-placeholder.png
rename to docs/test/media/navigate/test-plans-placeholder.png
diff --git a/docs/test/media/navigate/test-point-node-context-menu.png b/docs/test/media/navigate/test-point-node-context-menu.png
new file mode 100644
index 00000000000..5443eb4b16c
Binary files /dev/null and b/docs/test/media/navigate/test-point-node-context-menu.png differ
diff --git a/docs/test/media/navigate/test-suites-tree-import-test-suites-option.png b/docs/test/media/navigate/test-suites-tree-import-test-suites-option.png
new file mode 100644
index 00000000000..7ea40ee5f0c
Binary files /dev/null and b/docs/test/media/navigate/test-suites-tree-import-test-suites-option.png differ
diff --git a/docs/test/media/navigate/test-suites-tree.png b/docs/test/media/navigate/test-suites-tree.png
new file mode 100644
index 00000000000..2cb0a8f9c4c
Binary files /dev/null and b/docs/test/media/navigate/test-suites-tree.png differ
diff --git a/docs/test/media/navigate/view-linked-items.png b/docs/test/media/navigate/view-linked-items.png
new file mode 100644
index 00000000000..68b7cf9f4f7
Binary files /dev/null and b/docs/test/media/navigate/view-linked-items.png differ
diff --git a/docs/test/media/new-test-plans-page/copy-test-cases.png b/docs/test/media/new-test-plans-page/copy-test-cases.png
deleted file mode 100644
index b78d15a3a5c..00000000000
Binary files a/docs/test/media/new-test-plans-page/copy-test-cases.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/copy-test-plan.png b/docs/test/media/new-test-plans-page/copy-test-plan.png
deleted file mode 100644
index 98de535f53a..00000000000
Binary files a/docs/test/media/new-test-plans-page/copy-test-plan.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/define-tab-context-menu.png b/docs/test/media/new-test-plans-page/define-tab-context-menu.png
deleted file mode 100644
index 25ef85d579a..00000000000
Binary files a/docs/test/media/new-test-plans-page/define-tab-context-menu.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/define-tab-toolbar.png b/docs/test/media/new-test-plans-page/define-tab-toolbar.png
deleted file mode 100644
index 78618d0a33e..00000000000
Binary files a/docs/test/media/new-test-plans-page/define-tab-toolbar.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/execute-tab-context-menu.png b/docs/test/media/new-test-plans-page/execute-tab-context-menu.png
deleted file mode 100644
index 26d0c002a07..00000000000
Binary files a/docs/test/media/new-test-plans-page/execute-tab-context-menu.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/execute-tab-toolbar.png b/docs/test/media/new-test-plans-page/execute-tab-toolbar.png
deleted file mode 100644
index 0efc0a720fc..00000000000
Binary files a/docs/test/media/new-test-plans-page/execute-tab-toolbar.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/import-test-suites.png b/docs/test/media/new-test-plans-page/import-test-suites.png
deleted file mode 100644
index f24d80a1706..00000000000
Binary files a/docs/test/media/new-test-plans-page/import-test-suites.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/test-plan-header.png b/docs/test/media/new-test-plans-page/test-plan-header.png
deleted file mode 100644
index 47d011bf043..00000000000
Binary files a/docs/test/media/new-test-plans-page/test-plan-header.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/test-suites-tree.png b/docs/test/media/new-test-plans-page/test-suites-tree.png
deleted file mode 100644
index 5eec304dc8b..00000000000
Binary files a/docs/test/media/new-test-plans-page/test-suites-tree.png and /dev/null differ
diff --git a/docs/test/media/new-test-plans-page/view-linked-items.png b/docs/test/media/new-test-plans-page/view-linked-items.png
deleted file mode 100644
index 01803365447..00000000000
Binary files a/docs/test/media/new-test-plans-page/view-linked-items.png and /dev/null differ
diff --git a/docs/test/navigate-test-plans.md b/docs/test/navigate-test-plans.md
new file mode 100644
index 00000000000..210319db662
--- /dev/null
+++ b/docs/test/navigate-test-plans.md
@@ -0,0 +1,271 @@
+---
+title: Navigate Test Plans
+description: Learn how to navigate Test Plans.
+ms.technology: devops-test
+ms.topic: conceptual
+ms.author: kaelli
+author: KathrynEE
+ms.date: 09/09/2021
+monikerRange: '>=azure-devops-2020'
+---
+
+
+# Navigate Test Plans
+
+[!INCLUDE [version-2020-rtm](includes/version-2020-rtm.md)]
+
+Learn how to navigate Test Plans to support your test goals and operations. Use the following sections of the Test Plans page to accomplish the corresponding tasks.
+
+- **Test plan header**: Locate, favorite, edit, copy or clone a test plan.
+- **Test suites tree**: Add, manage, export, or order test suites. Leverage this to also assign configurations and perform user acceptance testing.
+- **Define tab**: Collate, add, and manage test cases in a test suite of choice via this tab.
+- **Execute tab**: Assign and execute tests via this tab or locate a test result to drill into.
+- **Chart tab**: Track test execution and status via charts, which can also be copied to dashboards.
+
+:::image type="content" source="media/navigate/test-plan-overview-2.png" alt-text="Test plans page, navigation elements.":::
+
+To learn about specific test artifacts, see the following articles:
+- [Create test plans and test suites](create-a-test-plan.md)
+- [Create manual test cases](create-test-cases.md)
+- [Test settings](/test-different-configurations.md)
+
+
+[!INCLUDE [prerequisites](includes/prerequisites.md)]
+
+> [!NOTE]
+> Most operations under the **Define** tab are only available to users with [Basic + Test Plans](https://marketplace.visualstudio.com/items?itemName=ms.vss-testmanager-web) access level or equivalent. Most operations under the **Execute** tab can be exercised by users granted a **Basic** access level.
+
+
+
+
+## Test plan header
+
+:::image type="content" source="media/navigate/test-plan-header.png" alt-text="test plan header page":::
+
+### Test plan tasks
+
+Use the Test Plan header, to do one of the following tasks:
+
+- Mark or unmark a test plan as a favorite
+- Easily navigate among your favorite test plans
+- View the iteration path of the test plan, which clearly indicates if the test plan is **Current** or **Past**
+- Navigate to the Test Progress report via the **View report** link
+- Navigate back to the **All/Mine** Test Plans page by choosing :::image type="icon" source="media/navigate/all-test-plans-icon.png" border="false"::: **All test plans**.
+
+
+### Test plan context menu options
+
+Choose the :::image type="icon" source="../media/icons/more-actions.png" border="false"::: **More options** to open the context menu for the Test Plan to perform one of the following actions:
+
+- **Copy test plan**: Quickly copy the current test plan.
+- **Edit test plan**: Edit the Test Plan work item form to define work item fields or add to the description or discussion.
+- **Test plan settings**: Configure the Test Run settings (to associate build or release pipelines) and the Test Outcome settings.
+
+:::image type="content" source="media/navigate/test-plan-header.png" alt-text="Test plan content menu options.":::
+
+## Configure test plan settings
+
+Choose **Test plan settings** to configure test runs or test outcomes.
+
+:::image type="content" source="media/navigate/test-plan-settings-dialog-undefined.png" alt-text="Test plan settings dialog, undefined.":::
+
+### Copy test plan
+
+We recommend creating a new Test Plan per sprint/release. When doing so, generally you can copy the Test Plan for the prior cycle and with few changes the copied test plan is ready for the new cycle. Use the **Copy test plan** menu option. This option lets you copy or clone test plans within a project.
+
+:::image type="content" source="media/navigate/copy-test-plan.png" alt-text="copy test plan page":::
+
+
+
+
+
+## Test suites header and tree
+
+:::image type="content" source="media/navigate/test-suites-tree.png" alt-text="Test suites tree menu options":::
+
+### Test suites header tasks
+
+The Test suite header allows you to perform the following tasks:
+
+- **Expand/collapse**: Choose the :::image type="icon" source="media/navigate/expand-collapse-icons.png" border="false"::: **Expand All/Collapse All** toolbar options to expand or collapse the suite hierarchy tree.
+- **Show test points from child suites**: Choose the :::image type="icon" source="media/navigate/show-test-points-from-child-nodes-icon.png" border="false"::: **Show test points from child suites** toolbar option, which is only visible when you are in the **Execute** tab, to view all the test points for the given suite and its children in one view for easier management of test points without having to navigate to individual suites one at a time.
+- **Order suites**: Drag/drop suites to either reorder the hierarchy of suites or move them from one suite hierarchy to another within the test plan.
+
+
+### Test suites context menu options
+
+Choose the :::image type="icon" source="../media/icons/more-actions.png" border="false"::: **More options** to open the context menu for the Test Suite and perform one of the following actions:
+
+- **Create new suites**: You can create one of three different types of suites:
+ - Choose **Static suite** to organize your tests within a folder suite.
+ - Choose **Requirement-based suite** to directly link to the requirements/user stories for seamless traceability.
+ - Choose **Query-based suite** to dynamically organize test cases that meet a query criteria.
+- **Assign configurations**: Assign configurations for the suite. For example, assign *Chrome*, *Firefox*, *EdgeChromium*, which then become applicable to all existing or new test cases that you add later to the suite.
+- **Export**: Export the test plan properties, test suite properties along with details of the test cases and test points as either an email or print to pdf.
+- **Open test suite work item**: This option allows you to edit the Test suite work item form to manage the work item fields.
+- **Assign testers to run all tests**: This option is very useful for User Acceptance testing (UAT) scenarios where the same test needs to be run/executed by multiple testers, generally belonging to different departments.
+- **Rename/Delete**: These options allow you to manage the suite name or remove the suite and its content from the test plan.
+- **Import test suites**: Use this option to import test cases present in other suites from same or other test plans and even across projects. More details below.
+
+
+**Export test suite dialog**
+:::image type="content" source="media/navigate/export-dialog.png" alt-text="Define tab, Export test suite dialog.":::
+
+**Import test suites**
+
+Reuse the suites you have created and import them into the current suite/plan. You can select the **Project**, **Test Plan**, and **Test Suite** from which you want to import the tests. Depending upon the suite you select, the entire hierarchy of that suite and corresponding test cases are imported into the current plan. Note that the test cases are added as a reference and not a clone or copy.
+
+:::image type="content" source="media/navigate/import-test-suites-dialog.png" alt-text="Test suites tree import overview.":::
+
+
+
+
+
+
+## Define and organize test cases
+
+From the **Define** tab, you can collate, add, and manage test cases for a test suite. Whereas you use the [**Execute** tab](#executetab) for assigning test points and executing them.
+
+:::image type="content" source="media/navigate/define-tab-tasks.png" alt-text="Define tab task overview.":::
+
+
+### Define test case tasks
+
+From the **Define** tab you can exercise the following tasks:
+
+- **New Test Case**:
+ - **Add Test Case**: Create a new test case using the work item form and automatically add it to the suite.
+ - **Add existing test cases**: Open a dialog to query for existing test cases that you can select from and add to the test suite.
+ - **Add New test case using grid**: Create one or more test cases using the test cases grid view and automatically add them to the suite.
+- **Order test cases**: Reorder test cases by dragging/dropping one or more test cases within a given suite. The order of test cases only applies to manual test cases and not to automated tests.
+- **Move test cases from one suite to another**: Using drag/drop, move test cases from one test suite to another.
+
+**Add existing test cases to a test suite dialog**
+
+:::image type="content" source="media/navigate/add-test-cases-to-suite-dialog.png" alt-text="**Define** tab, add existing test cases dialog.":::
+
+### Define tab toolbar options
+
+:::image type="content" source="media/navigate/define-tab-toolbar-2.png" alt-text="**Define** tab, toolbar options.":::
+
+From the **Define** tab, toolbar, you can exercise the following options:
+
+- **Export test cases to CSV**: Export existing test cases to a CSV file and make changes using Excel.
+- **Import test cases from CSV**: Import changes made to test cases from a CSV file.
+- **Grid View**: Use the grid mode for viewing or editing multiple test cases along with test steps.
+- **Toggle full screen mode**: Expand the view by choosing full screen mode.
+- **Filter**: Choose :::image type="icon" source="media/navigate/filter-icon.png" border="false"::: **Filter** to toggle the filter toolbar to filter the list of test cases.
+- **Column options**: Add or remove fields to display and sort on. The list of columns available for selection are primarily the fields from the test case work item form.
+
+### Define test case context menu options
+
+:::image type="content" source="media/navigate/define-tab-context-menu.png" alt-text="Define tab context menu page.":::
+
+The context menu on the Test case node within the **Define** tab provides the following options:
+
+- **Open/edit test case work item form**: This option allows you to edit a Test case using the work item form wherein you edit the work item fields including test steps.
+- **Edit test cases**: This option allows you to bulk edit Test case work item fields. However, you cannot use this option to bulk edit test steps.
+- **Edit test cases in grid**: This option allows you to bulk edit the selected test cases including test steps using the grid view.
+- **Assign configurations**: This option allows you to override the suite level configurations with test case level configurations.
+- **Remove test cases**: This option allows you to remove the test cases from the given suite. It does not change the underlying test case work item though.
+- **Create a copy/clone of test cases**: Create a copy or clone selected test cases.
+- **View linked items**: Review items linked to a test case.
+
+### Copy or clone test cases
+
+Choose **Copy test case** to copy or clone a test case. Specify the destination project, destination test plan and destination test suite in which to create the copy/cloned test case. In addition, you can also specify whether you want to include existing links/attachments to flow into the cloned copy.
+
+:::image type="content" source="media/navigate/copy-test-cases.png" alt-text="Define tab copy test cases menu option and dialog.":::
+
+
+### View linked item
+
+Use **View linked items** option, to review objects linked to the test case. Choose each tab to view the links listed under the linked object type:
+- **Test Suites**
+- **Requirements**: Includes any work item that belongs to the Requirements Category, such as User Stories (Agile), Product Backlog Items (Scrum), Requirements (CMMI), or a custom work item type.
+- **Bugs**: Includes bugs that have been filed as part of test execution and any work items that belong to the Bug Category that have been linked to the test case.
+
+:::image type="content" source="media/navigate/view-linked-items.png" alt-text="Define tab, View linked items dialog.":::
+
+
+### Bulk update using the Grid view
+
+Choose the :::image type="icon" source="media/navigate/grid-icon.png" border="false"::: **Grid View** to perform bulk updates to the test cases.
+
+:::image type="content" source="media/navigate/grid-view.png" alt-text="Define tab, grid view.":::
+
+Click within a cell to edit the text in that cell. Right-click within a cell to choose an option to **Insert row**, **Delete row**, or **Clear row**. Choose :::image type="icon" source="media/navigate/bulk-save-icon.png" border="false"::: **Save test cases** to perform a bulk save of your changes. Or, choose :::image type="icon" source="media/navigate/grid-refresh.png" border="false"::: **Refresh** to clear your changes. When complete, choose **Close Grid**.
+
+:::image type="content" source="media/navigate/grid-view-cell-options.png" alt-text="Define tab, grid view, cell options.":::
+
+
+
+## Execute tests
+
+Use the **Execute** tab to assign test points or run tests.
+
+:::image type="content" source="media/navigate/execute-tab-test-points-overview.png" alt-text="Execute tab overview.":::
+
+**What is a test point?** Test cases by themselves are not executable. When you add a test case to a test suite then test point(s) are generated. A test point is a unique combination of test case, test suite, configuration, and tester.
+For example, if you have a test case named *Test login functionality* and you add two configurations for the Edge and Chrome browsers, you have two test points. You can execute or run each of these test points. On execution, test results are generated. Through the test results view, or execution history, you can see all executions of a test point. The latest execution for the test point is what you see in the **Execute** tab.
+
+Test cases are reusable entities. By including them in a test plan or suite, test points are generated. By executing test points, you determine the quality of the product or service under development.
+
+
+### Execute tasks
+
+From the **Execute** tab you can do one of the following tasks:
+
+- **Bulk mark test points**: Quickly mark the outcome of or more test points—**Passed**, **Failed**, **Blocked** or **Not Applicable**—without having to run the test case via the Test runner.
+- **Run test points**:Run the test cases by individually going through each test step and marking them pass/fail using a Test runner. Depending upon the application you are testing, you can use the **Web Runner** for testing a "web application" or the **Desktop Runner** for testing desktop or web applications. Invoke **Run with options** to specify a **Build** against which the testing you want to perform.
+- **Column options**: Add or remove columns. The list of columns available for selection are associated with test points, such as Run by, Assigned Tester, Configuration, etc.
+- **Toggle Full screen view**: View the contents of the page in a full screen mode.
+- **Filter**: Filter the list of test points using the fields of a test case **Title**, **ID**, **Outcome**, **Tester**, **Configuration**, **Assigned To**, or **State**. You can also sort the list by choosing a column header.
+
+
+### Change column options
+
+Choose :::image type="icon" source="media/navigate/column-options-icon.png" border="false"::: **Column options** to open the Column options dialog. Add or remove columns and drag and drop them in the order you want.
+
+:::image type="content" source="media/navigate/column-options.png" alt-text="Column options dialog.":::
+
+
+### Test Points context menu options
+
+:::image type="content" source="media/navigate/test-point-node-context-menu.png" alt-text="Execute tab, test point node More options menu.":::
+
+Choose the :::image type="icon" source="../media/icons/more-actions.png" border="false"::: **More options** to open the context menu for a Test Point node to perform one of the following actions:
+
+- **View execution history**: View the execution history for the test case in a side pane. You can move across the test points or open the detailed execution history from the pane.
+- **Mark Outcome**: Quickly mark the outcome of the test points—**Passed**, **Failed**, **Blocked** or **Not Applicable**.
+- **Run** - Initiate a test runner with options to **Run for web application**, **Run for desktop**, **Run with options**.
+- **Reset test to active**: Reset the test outcome to **Active**, ignoring the last outcome of the test point.
+- **Edit test case**: Open the work item form, optionally edit work item fields including test steps.
+- **Assign tester**: Assign the test points to a tester for test execution.
+
+To learn more about executing tests, see [Run manual tests](run-manual-tests.md) and [Run automated tests from test plans](run-automated-tests-from-test-hub.md).
+
+
+## Chart test cases and test results
+
+From the chart tab you can create various test case or test result charts. To learn how, see [Track test status, Charts](track-test-status.md#charts).
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Create test plans and test suites](create-a-test-plan.md)
+
+
+## Related articles
+
+- [Run manual tests](run-manual-tests.md)
+- [Run automated tests from test plans](run-automated-tests-from-test-hub.md)
+- [Track test status](track-test-status.md).
+- [About pipeline tests](../pipelines/test/test-glossary.md)
+- [What are extensions?](../extend/overview.md)
+- [Test Planning and Management Guide](/archive/blogs/visualstudioalmrangers/test-planning-and-management-guide-updated).
+
+
+### REST APIs
+
+- [Test Management REST API](/rest/api/azure/devops/test)
diff --git a/docs/test/new-test-plans-page.md b/docs/test/new-test-plans-page.md
deleted file mode 100644
index c0cd337656e..00000000000
--- a/docs/test/new-test-plans-page.md
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: New test plans page
-description: New Test Plans page
-ms.assetid: FFBBD2F9-C1C5-4273-916A-28834B794CC3
-ms.technology: devops-test
-ms.topic: conceptual
-ms.author: sdanie
-author: steved0x
-ms.date: 06/12/2020
-monikerRange: '>=azure-devops-2020'
----
-# New Test Plans page
-
-[!INCLUDE [version-2020-rtm](includes/version-2020-rtm.md)]
-
-[!INCLUDE [feature-availability](includes/feature-availability.md)]
-
-A new Test Plans Page (Test Plans*) for your planned testing needs is available for Azure DevOps Services and Azure DevOps Server 2020. The new page provides you with streamlined views to help you focus on the task at hand - be it test planning, authoring, execution, or tracking. It is also clutter-free and consistent with the rest of Azure DevOps offering. We hope that you find it easy and intuitive to use.
-
-This new page has been in public preview for past few quarters and is the default for all Test Plans users. During this time, we have continued to add the missing features/capabilities and address the feedback you have been providing us. We are almost towards the end of this journey and now are ready to pull out the old page by **the end of November 2020**. We highly recommend leveraging the new page and [sharing your feedback](#feedback) with us. However, if you absolutely need to leverage the prior page then enable it using the information provided in [Manage or enable features](../project/navigation/preview-features.md).
-
-## Overview
-
-
-> [!NOTE]
-> Any action performed in either page will reflect on the other too since the backend data store is the same.
-
-
-:::image type="content" source="media/new-test-plans-page/test-plan-overview.png" alt-text="test plan overview page":::
-
-The new Test Plans page has total of six sections of which the first four are new, while the Charts & Extensibility sections are the existing functionality.
-1. **Test plan header**: Use this to locate, favorite, edit, copy or clone a test plan.
-2. **Test suites tree**: Use this to add, manage, export, or order test suites. Leverage this to also assign configurations and perform user acceptance testing.
-3. **Define tab**: Collate, add, and manage test cases in a test suite of choice via this tab.
-4. **Execute tab**: Assign and execute tests via this tab or locate a test result to drill into.
-5. **Chart tab**: Track test execution and status via charts, which can also be pinned to dashboards.
-6. **Extensibility**: Supports the [current extensibility points](../extend/overview.md) within the product.
-
-Lets take a broad stroke view of these new sections below.
-
-
-
-
-## Test plan header
-
-:::image type="content" source="media/new-test-plans-page/test-plan-header.png" alt-text="test plan header page":::
-
-**Tasks**
-
-The Test Plan header allows you to perform the following tasks:
-
-- Mark a test plan as favorite
-- Unmark a favorited test plan
-- Easily navigate among your favorite test plans
-- View the iteration path of the test plan, which clearly indicates if the test plan is Current or Past
-- View the quick summary of the Test Progress report with a link to navigate to the report
-- Navigate back to the All/Mine Test Plans page
-
-
-**Context menu options**
-
-The context menu on the Test Plan header provides the following options:
-
-- *Copy test plan*: This is a new option that allows you to quickly copy the current test plan. More details below.
-- *Edit test plan*: This option allows you to edit the Test Plan work item form to manage the work item fields.
-- *Test plan settings*: This option allows you to configure the Test Run settings (to associate build or release pipelines) and the Test Outcome settings
-
-
-***Copy test plan (new capability)***
-
-:::image type="content" source="media/new-test-plans-page/copy-test-plan-dialog.png" alt-text="copy test plan page":::
-
-We recommend creating a new Test Plan per sprint/release. When doing so, generally the Test Plan for the prior cycle can be copied over and with few changes the copied test plan is ready for the new cycle. To make this process easy, we have enabled a 'Copy test plan' capability on the new page. By leveraging 'Copy test plan' capability, you can copy or clone test plans within the project. Its backing REST API is covered [here](/rest/api/azure/devops/testplan/test%20plan%20clone/clone%20test%20plan?view=azure-devops-rest-5.1&preserve-view=true). The API lets you copy/clone a test plan across projects too.
-For more guidelines on Test Plans usage, refer [here](/archive/blogs/visualstudioalmrangers/test-planning-and-management-guide-updated).
-
-
-
-
-## Test suites tree
-
-:::image type="content" source="media/new-test-plans-page/test-suites-tree.png" alt-text="test suites tree page":::
-
-**Tasks**
-
-The Test suite header allows you to perform the following tasks:
-
-- *Expand/collapse*: This toolbar option allows you to expand or collapse the suite hierarchy tree.
-- *Show test points from child suites*: This toolbar option is only visible when you are in the "Execute" tab. This allows you to view all the test points for the given suite and its children in one view for easier management of test points without having to navigate to individual suites one at a time.
-- *Order suites*: You can drag/drop suites to either reorder the hierarchy of suites or move them from one suite hierarchy to another within the test plan.
-
-
-**Context menu options**
-
-The context menu on the Test suites tree provides the following options:
-
-- *Create new suites*: You can create three different types of suites as follows:
- - Use static suite or folder suite to organize your tests.
- - Use requirement-based suite to directly link to the requirements/user stories for seamless traceability.
- - Use query-based to dynamically organize test cases that meet a query criteria.
-- *Assign configurations*: You can assign configurations for the suite (example: Chrome, Firefox, EdgeChromium) and these would then be applicable to all the existing test cases or new test cases that you add later to this suite.
-- *Export as pdf/email*: Export the Test plan properties, test suite properties along with details of the test cases and test points as either "email" or "print to pdf".
-- *Open test suite work item*: This option allows you to edit the Test suite work item form to manage the work item fields.
-- *Assign testers to run all tests*: This option is very useful for User Acceptance testing (UAT) scenarios where the same test needs to be run/executed by multiple testers, generally belonging to different departments.
-- *Rename/Delete*: These options allow you to manage the suite name or remove the suite and its content from the test plan.
-- *Import test suites*: Use this option to import test cases present in other suites from same or other test plans and even across projects. More details below.
-
-
-***Import test suites (new capability)***
-
-:::image type="content" source="media/new-test-plans-page/import-test-suites.png" alt-text="test suites tree import page":::
-
-It is now easier to reuse the suites you have created already and import them into the current suite/plan. You can select the project, test plan, and test suite from which you want to import the tests. Depending upon the suite selected, the entire hierarchy of that suite and corresponding test cases are imported into the current plan. Note that the test cases are added as a reference and not a clone/copy.
-
-
-
-
-## Define tab
-
-:::image type="content" source="media/new-test-plans-page/define-tab-toolbar.png" alt-text="define tab page":::
-
-Define tab lets you collate, add, and manage test cases for a test suite. Whereas the execute tab is for assigning test points and executing them.
-
-> The Define tab and certain operations are only available to users with [Basic + Test Plans](https://marketplace.visualstudio.com/items?itemName=ms.vss-testmanager-web) access level or equivalent. Everything else should be exercisable by a user with 'Basic' access level.
-
-
-**Tasks**
-
-The Define tab allows you to perform the following tasks:
-
-- *Add New test case using work item form*: This option allows you to create a new test case using the work item form. The test case created will automatically be added to the suite.
-- *Add New test case using grid*: This option allows you to create one or more test cases using the test cases grid view. The test cases created will automatically be added to the suite.
-- *Add Existing test cases using a query*: This option allows you to add existing test cases to the suite by specifying a query.
-- *Order test cases by drag/drop*: You can reorder test cases by dragging/dropping of one or more test cases within a given suite. The order of test cases only applies to manual test cases and not to automated tests.
-- *Move test cases from one suite to another*: Using drag/drop, you can move test cases from one test suite to another.
-- *Export / Import as CSV*: Using this option, you can export the existing test cases to Excel CSV file, make changes to the CSV file and then import the file back into the suite. This has been one of the most requested features and we are happy to share that we are opening this for beta testing. See [here for more options.](https://pkuma-msft.github.io/azure-test-plans/articles/testcase-import-export-csv.html)
-- *Show grid*: You can use the grid mode for viewing/editing test cases along with test steps.
-- *Full screen view*: You can view the contents of the entire Define tab in a full screen mode using this option.
-- *Filtering*: Using the filter bar, you can filter the list of test cases using the fields of "test case title", "assigned to" and "state". You can also sort the list by clicking on the column headers.
-- *Column options*: You can manage the list of columns visible in the Define tab using "Column options". The list of columns available for selection are primarily the fields from the test case work item form.
-
-
-**Context menu options**
-
-:::image type="content" source="media/new-test-plans-page/define-tab-context-menu.png" alt-text="define tab context menu page":::
-
-The context menu on the Test case node within the Define tab provides the following options:
-
-- *Open/edit test case work item form*: This option allows you to edit a Test case using the work item form wherein you edit the work item fields including test steps.
-- *Edit test cases*: This option allows you to bulk edit Test case work item fields. However, you cannot use this option to bulk edit test steps.
-- *Edit test cases in grid*: This option allows you to bulk edit the selected test cases including test steps using the grid view.
-- *Assign configurations*: This option allows you to override the suite level configurations with test case level configurations.
-- *Remove test cases*: This option allows you to remove the test cases from the given suite. It does not change the underlying test case work item though.
-- *Create a copy/clone of test cases*: This option allows you to create a copy/clone of selected test cases. See below for more details.
-- *View linked items*: This option allows you to look at the linked items for a given test case. See below for more details.
-
-
-***Copy/clone test cases (new capability)***
-
-:::image type="content" source="media/new-test-plans-page/copy-test-cases.png" alt-text="define tab copy test cases page":::
-
-For scenarios where you want to copy/clone a test case, you can use the "Copy test case" option. You can specify the destination project, destination test plan and destination test suite in which to create the copy/cloned test case. In addition, you can also specify whether you want to include existing links/attachments to flow into the cloned copy.
-
-
-***View linked items (new capability)***
-
-:::image type="content" source="media/new-test-plans-page/view-linked-items.png" alt-text="define tab view linked items page":::
-
-Traceability among test artifacts, requirements and bugs is a critical value proposition of the Test Plans product. Using the "View linked items" option, you can easily look at all the linked Requirements that this test case is linked with, all the Test suites/Test plans where this test case has been used and all the bugs that have been filed as part of test execution.
-
-
-
-
-## Execute tab
-
-:::image type="content" source="media/new-test-plans-page/execute-tab-toolbar.png" alt-text="execute tab page":::
-
-Define tab lets you collate, add and manage test cases for a test suite. Whereas the execute tab is for assigning test points and executing them.
-
-**What is a test point?** Test cases by themselves are not executable. When you add a test case to a test suite then test point(s) are generated. A test point is a unique combination of test case, test suite, configuration, and tester. Example: if you have a test case as "Test login functionality" and you add 2 configurations to it as Edge and Chrome then this results in 2 test points. Now these test points can be executed. On execution, test results are generated. Through the test results view (execution history) you can see all executions of a test point. The latest execution for the test point is what you see in the execute tab.
-Hence, test cases are reusable entities. By including them in a test plan or suite, test points are generated. By executing test points, you determine the quality of the product or service being developed.
-
-One of the primary benefits of the new page is for users who mainly do test execution/tracking (need to have only 'Basic' access level), they are not overwhelmed by the complexity of suite management (define tab is hidden for such users).
-
-> The Define tab and certain operations are only available to users with [Basic + Test Plans](https://marketplace.visualstudio.com/items?itemName=ms.vss-testmanager-web) access level or equivalent. Everything else, including the "Execute" tab should be exercisable by a user with 'Basic' access level.
-
-
-**Tasks**
-
-The Execute tab allows you to perform the following tasks:
-
-- *Bulk mark test points*: This option allows you to quickly mark the outcome of the test points - passed, failed, blocked or not applicable, without having to run the test case via the Test runner. The outcome can be marked for one or multiple test points at one go.
-- *Run test points*: This option allows you to run the test cases by individually going through each test step and marking them pass/fail using a Test runner. Depending upon the application you are testing, you can use the "Web Runner" for testing a "web application" or the "desktop runner" for testing desktop and/or web applications. You can also invoke the "Run with options" to specify a Build against which the testing you want to perform.
-- *Column options*: You can manage the list of columns visible in the Execute tab using "Column options". The list of columns available for selection are associated with test points, such as Run by, Assigned Tester, Configuration, etc.
-- *Full screen view*: You can view the contents of the entire Execute tab in a full screen mode using this option.
-- *Filtering*: Using the filter bar, you can filter the list of test points using the fields of "test case title", "assigned to", "state", "test outcome", "Tester" and "Configuration". You can also sort the list by clicking on the column headers.
-
-
-**Context menu options**
-
-:::image type="content" source="media/new-test-plans-page/execute-tab-context-menu.png" alt-text="execute tab context menu page":::
-
-The context menu on the Test point node within the Execute tab provides the following options:
-
-- *Mark test outcome*: Same as above, allows you to quickly mark the outcome of the test points - passed, failed, blocked or not applicable.
-- *Run test points*: Same as above, allows you to run the test cases via test runner.
-- *Reset test to active*: This option allows you to reset the test outcome to active, thereby ignoring the last outcome of the test point.
-- *Open/edit test case work item form*: This option allows you to edit a Test case using the work item form wherein you edit the work item fields including test steps.
-- *Assign tester*: This option allows you to assign the test points to testers for test execution.
-- *View test result*: This option allows you to view the latest test outcome details including the outcome of each test step, comments added or bugs filed.
-- *View execution history*: This option allows you to view the execution history for the test case in a side panel. You can move across the test points or open the detailed execution history from the panel - refer below image
-
-:::image type="content" source="media/new-test-plans-page/execute-tab-execution-history.png" alt-text="execute tab execution history":::
-
-
-
-## Provide feedback
-Thank you for all the feedback you have provided on this page. We have tried to address most of the feedback submitted and have filled all the functionality gaps. As such, we are reaching towards the end of this journey and plan to pull out the old page soon.
-
-Reach us at [community forum](https://developercommunity.visualstudio.com/content/problem/post.html?space=21) for any queries. In the process, share screenshots as appropriate.
diff --git a/docs/test/toc.yml b/docs/test/toc.yml
index 3e4209ce2e2..4f43fe34bbb 100644
--- a/docs/test/toc.yml
+++ b/docs/test/toc.yml
@@ -7,6 +7,9 @@
- name: Get started
expanded: true
items:
+ - name: Navigate Test Plans
+ href: navigate-test-plans.md
+ displayName: test suites tree, define, execute, chart
- name: Create a test plan
href: create-a-test-plan.md
displayName: create, plan
@@ -21,9 +24,6 @@
displayName: access, permissions
- name: Manual testing
items:
- - name: New test plans page
- href: new-test-plans-page.md
- displayName: test plans, new,
- name: Test from the Kanban board
href: ../boards/boards/add-run-update-tests.md?toc=/azure/devops/test/toc.json&bc=/azure/devops/test/breadcrumb/toc.json
displayName: kanban, tesr, board
diff --git a/docs/test/track-test-status.md b/docs/test/track-test-status.md
index c51a436eeec..3f9e00552eb 100644
--- a/docs/test/track-test-status.md
+++ b/docs/test/track-test-status.md
@@ -21,6 +21,7 @@ View the status of your planned testing using an out-of-the-box Progress Report
:::moniker range=">= azure-devops-2020"
## Progress Report
+
To track the progress of more than one test plan or test suite, use the Progress Report. It helps you track the team's progress with respect to planned testing of your product or service by answering the following questions:
1. How much testing is complete?
2. What is the current status - how many tests have passed, failed or are blocked?
@@ -30,11 +31,13 @@ To track the progress of more than one test plan or test suite, use the Progress
6. View the progress each suite has made within a test plan and identify the areas that need attention.
### Configuring the report
+
By navigating to Test Plans > Progress Report, you can start using the report. It requires no setup and is applicable for all Azure DevOps Services organizations. When you view the report, it shows you the status of the test plan you had accessed last. However, using the filter bar, you can select one or more test plans in the project.
### Understanding the report
+
The progress report consists of three sections:
-1. **Summary**: This section provides you with a consolidated view for the selected test plans. To understand what test points are, refer [here](new-test-plans-page.md).
+1. **Summary**: This section provides you with a consolidated view for the selected test plans. To understand what test points are, see [Navigate Test Plans](navigate-test-plans.md).
2. **Outcome trend**: This graph renders a daily snapshot to give you an execution and status trendline. It can show data for 14 days (default), 30 days, or a custom range of your choice. Data for today may or may not appear in this chart based on the time of the day you are looking at the report.
3. **Details**: This section lets you drill down by each test plan and gives you summary of each test suite in it. The section also lets you navigate to a test plan or suite of choice by double-clicking on it.