
In the test suite, we can see all of the linked work items, which happen to be the test cases.

Locate the Related Work panel and note that this test case is linked to the suite it belongs to. This dialog provides all the info you need on this test case.

Double-click the Verify that user is allowed to save his credit card detail test case. On the right side you can see that this test suite has three test cases designed to confirm expected behavior of the feature implementation. Note that the work item numbers will vary every time you generate demo data for a lab. This suite of tests focuses on that work item, which happens to be a feature. Select the suite of tests for the story As a customer, I would like to store my credit card details securely. Select the Parts Unlimited_TestPlan1 test plan.

The Parts Unlimited project has one test plan, which is under the Parts Unlimited Team and called Parts Unlimited_TestPlan1. Each test case is designed to confirm a specific behavior and may belong to one or more test suites. Within each test plan are test suites, which are collections of test cases (and optionally other test suites) designed to validate a work item, such as a feature implementation or bug fix. In general, every major milestone in a project should have its own test plan. The test hub provides a central place for all test planning, execution, and analysis. Select Test Plans to navigate to the Test Hub. Navigate to your team project on Azure DevOps. Task 1: Understanding Test Plans, Suites and Cases In this exercise, you will learn how to create and manage test plans, test suites and test cases.

You will also create and execute manual tests that can be consistently reproduced over the course of each release. This project will guide you through creating test plans designed to efficiently validate your software milestones. In this lab, you will learn how to use Azure DevOps to manage your project’s testing lifecycle.
