Home / Test Planning and Management with Azure Test Plans

Overview

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

Prerequisites

  • This lab requires you to complete tasks 1 and 2 from the prerequisite instructions.

Exercise 1: Managing Test Plans, Suites, and Cases

In this exercise, you will learn how to create and manage test plans, test suites, and test cases.

Task 1: Understanding Test Plans, Suites, and Cases

  1. Navigate to your team project on Azure DevOps.

  2. Select Test Plans to navigate to the Test Hub. The test hub provides a central place for all test planning, execution, and analysis.

  3. In general, every major milestone in a project should have its own test plan. 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. Each test case is designed to confirm a specific behavior and may belong to one or more test suites. The Parts Unlimited project has one test plan, which is under the Parts Unlimited Team and called Parts Unlimited_TestPlan1. Select the Parts Unlimited_TestPlan1 test plan.

  4. Select the suite of tests for the story As a customer, I would like to store my credit card details securely. This suite of tests focuses on that work item, which happens to be a feature. Note that the work item numbers will vary every time you generate demo data for a lab.

  5. On the right side you can see that this test suite has three test cases designed to confirm expected behavior of the feature implementation. Double-click the Verify that user is allowed to save his credit card detail test case.

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

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

  8. However, it’s not yet associated with the feature it’s designed to test, which we can link now. Click Add link | Existing item.

  9. Set the Link type to Parent and search for “credit card”.

  10. Select the Feature for Credit Card Purchase.

  11. Click OK.

  12. The parent feature is now associated with the suite that tests it, and anyone can navigate between them to view their relationship relative to the other work items involved.

  13. Click Save & Close.

  14. Dismiss the original test case dialog.

Task 2: Managing Tests

  1. Sometimes a set of test cases should be run in a specific order to maximize efficiency. Click Order tests to specify the order these test cases should be run.

  2. While these test cases could be run separately to confirm the behavior, it probably makes more sense to run the test case that rejects invalid cards first. Then, the tester can confirm that a valid card can be saved, followed by the test case for editing a saved card. Drag and drop the second test case above the first and click Done.

  3. You can now see that the Order has been updated and that the list is now sorted by it.

  4. Another significant aspect of testing has to do with the environment each test is run in. For this web app, the browser and operating system are key considerations. Right now all the tests only use one configuration: Windows 10.

  5. Select the Configurations tab.

  6. Note that there is one existing configuration for Windows 10. Each test configuration includes a name and a description, as well as a set of customizable Configuration variables. This project has one configuration variable set for Operating System. You can easily add more and/or edit the available entries for each. Click Add configuration variable.

  7. Select the Browser variable and set it to Microsoft Edge.

  8. Click Save to save the configuration.

  9. Now let’s suppose the test team has acquired an iPhone X and wants to add it into the test matrix. It’s really easy to register this environment as a new configuration so that test cases can specify it. However, before adding it, we’ll need an Operating System option for iOS 10. Click the Operating System configuration variable.

  10. Click Add new value and add an entry for iOS 12.

  11. Click Save.

  12. Now we have everything we need to add the iPhone X. Click the Add dropdown and select New test configuration.

  13. Set the Name to “iPhone X”.

  14. Click Add configuration variable twice and set the Browser to Safari and Operating System to iOS 12.

  15. Click Save to save the new configuration.

  16. Return to the Test Plans tab.

  17. Click the dropdown next to the test suite we’ve been working with so far and select Assign configurations to test suite.

  18. Check the iPhone X option and click Save.

  19. Notice that each test case has been duplicated with an additional configuration for iPhone X. Now each environment can be tested and tracked separately.

Task 3: Authoring Tests

  1. Expand the dropdown next to the test plan and select New static suite. A static suite of test cases is a suite where the cases have been manually assigned. You can also create suites based on common requirements (requirement-based suite) or a query of test cases and/or work items (query-based suite).

  2. Set the name of the new suite to “Shipping tests”. These tests will all focus on functionality related to shipping. Remember that you can easily share test cases across suites, so there’s minimal redundancy when having a lot of overlapping suites.

  3. Expand the dropdown next to the newly created suite and select New requirement-based suite.

  4. You could customize the query used to specify which requirements are retrieved, but just leave the defaults and click Run query. Locate and select the three product backlog items related to shipping. Click Create suites to create a test suite for each.

  5. Select one of the newly created suites, such as the one associated with tracking package status.

  6. While you can create test cases one at a time, it’s sometimes easier to use a grid layout to quickly add many test cases. In the test cases panel, select New | New test case using grid.

  7. Enter a few test cases and click the Save All button. The Title will be the eventual title of the test case. Step Action will be the first (and possibly only) step of the test. If that step has an expected result, you can specify it as Step Expected Result.

  8. You can optionally continue to add and edit work items in the grid view. When satisfied, return back to the list view by clicking the View: Grid toggle.

  9. The list view shows the same data, but in a different view.

  10. Another option to create suites is via work item query. Expand the dropdown next to the Shipping tests suite and select new query-based suite.

  11. Let’s say you wanted to create a set of test suites based on bugs related to shipping in the project. Change the Work Item Type to Microsoft.BugCategory to search for bugs and click Run query. You now have a list of bugs that you can select to create suites from, if you choose.

  12. Press Esc to close the dialog.

Exercise 2: Authoring, Running, and Analyzing Manual Tests

In this exercise, you will learn how to create a manual test plan and populate it with steps. The plan can later be run to confirm the expected behavior of your software. In this lab, we’re going to focus on creating a new manual test case and running it.

Task 1: Installing the Test & Feedback Extension

  1. Install Google Chrome from http://google.com/chrome. The rest of this exercise will use Chrome as its browser. If you’re already using Chrome, just open a new instance for the next set of steps.

  2. Navigate to the Visual Studio Marketplace at http://marketplace.visualstudio.com.

  3. Select the Visual Studio Team Services tab. Search for “feedback” and click the Test & Feedback extension.

  4. Click on Install button on the details page.

  5. Click Install for the Chrome extension.

  6. In the Chrome Web Store, click Add to Chrome.

  7. Confirm the installation when asked.

  8. To open the extension, click the extension icon that will appear on the right of the address bar. Select the Connection Settings tab. Enter the URL of your Azure DevOps instance, such as “https://MYTEAM.visualstudio.com”, as the Server URL and click Next.

  9. The extension can be used in two modes: Connected and Standalone mode. If you have Azure DevOps or Team Foundation Server (TFS), select Connected mode. Standalone mode is for users who don’t have Azure DevOps or TFS and want to use the extension to file bugs and share the report with their team.

  10. After connecting to Azure DevOps, you will need to select the team you want these efforts associated with. Select the Parts Unlimited Team under the Parts Unlimited project and click Save to continue.

Task 2: Authoring a Manual Test Plan

  1. In Chrome, navigate to your Parts Unlimited project.

  2. As before, navigate to the Test Plans hub.

  3. Expand the dropdown next to the test plan and select New static suite.

  4. Name the new suite “End-to-end tests” and press Enter.

  5. From the Tests tab, select New | New test case to create a new test case.

  6. In the Title box, type “Confirm that order number appears after successful order” as the name of the new test case.

  7. At this point, we’re ready to add steps to this manual test. Each step includes an Action, which describes the action the tester needs to perform. Optionally, a step can include an Expected Result, which describes the expected result of the given action. In the Steps panel, create a step for each of the following Actions, only one of which has an Expected Result.

    Action Expected Result
    Open project site  
    Click Brakes  
    Click Disk and Pad Combo  
    Click Add to Cart  
    Click Checkout  
    Enter @Email, @Password  
    Enter @Name, @Phone, @Email, @Address, @City, @State, @PostalCode, @Country, @Promo  
    Click Submit Order  
    Confirm order page has order # Order # should appear on order confirmation page
    Log out  
    Close browser  

    Note: If you end up with an extra empty step, delete it.

  8. At this point, the Steps panel should look similar to the following:

  9. Note the “Enter @Email, @Password” and “Enter @Name, @Phone, @Email, @Address, @City, @State, @PostalCode, @Country, @Promo” steps. In these steps, we used the @ sign to indicate that there were iteration-specific variables to be used during the manual test pass. We can define which variables to use by scrolling down to the Parameter Values section of this form and entering them for each iteration. Note that you may need to use the scroll bar on the far right side of the test case dialog to view this section.

  10. Use the following table to set up values for two iterations.

    Fields Iteration 1 Iteration 2
    Email admin@test.com sachin@test.com
    Password P@ssw0rd P@ssw0rd
    Name Admin User Sachin Raj
    Phone 425-555-1234 555-555-5555
    Address One Microsoft Way Two Tailspin Trail
    City Redmond Springfield
    State WA IL
    PostalCode 98052 11135
    Country USA USA
    Promo FREE FREE
  11. The Parameter Values section should now look like this. Note that you can enter as many iterations as you need to fully test the breadth of the scenario.

  12. Click Save & Close to save the test case.

Task 3: Running a Manual Test Plan

  1. In this task, you will learn how to run the manual test plan that we created earlier. Note that the process for triggering an automated test run follows a similar workflow. You can learn more about that in the documentation.

  2. Right-click the test case created earlier and select Run with options to begin a manual test run.

  3. There are a few options that you can use to customize each test run. The first option is to select a Runner, which will be the browser in this scenario. Next, you may have the option to specify which kinds of data to collect. Finally, you may optionally specify which build is being tested to make it easier to associate the results with the build they were from. Click OK to continue.

  4. If the Test Runner window does not appear, check to see if it was blocked by the pop-up blocker. If so, click the Pop-up blocker button, select Always allow pop-ups…, and then click Done. You can then launch the test run again with success.

  5. In the Test Runner window, expand the Test 1 of 1: Iteration 1 dropdown. Note that there are two iterations: one for each set of parameters specified in the test case. In the first iteration, the admin@test.com account is used. In the second, sachin@test.com will be used.

  6. The first step in the test is to open the project site. To do this, switch to the Visual Studio instance that has the Parts Unlimited solution loaded. From the IIS Express target dropdown, select Browse With….

  7. Select Google Chrome and click Browse.

  8. If you’re working on a large screen, it may be easier to resize the new window to fit next to the Test Runner window. Otherwise you can just switch back and forth.

  9. Once the site loads, return to the Test Runner and click the Pass test step button. As you complete the next steps of this test, be sure to check the Pass test step buttons for them as well.

  10. The next step is to click the Brakes menu item.

  11. Then click the Disk and Pad Combo product.

  12. The next step is to click Add to cart.

  13. On the next page, click Checkout.

  14. Log in using the credentials specified in the next step.

  15. Unfortunately, this will fail because there isn’t an admin@test.com account.

  16. The Test Runner provides three valuable ways to record media from a test run. The first option is to take screenshots. The second is to capture each user action in an image action log. The final is to record the screen as a video. Click the Capture screenshot button to take a screenshot.

  17. Crop the screen down to show the login form and error message. Specify the name “No admin account” and click the Confirm button.

  18. Right-click the failed step and select Add comment.

  19. Enter a comment of “Admin account does not exist by default” and fail the test using the Fail test step button.

  20. Click Create bug to log a new bug.

  21. Enter the bug title of “Admin account does not exist by default” and click Save & Close to log the bug.

  22. Since the test cannot be completed due to a bug not directly related to the functionality being tested, expand the Mark test case result dropdown and select Block test. Click Save and close to save the test run.

  23. Close the test browser windows.

Task 4: Analyzing Manual Test Results

  1. In this task, you will learn how to review the results of a manual test run.

  2. Return to the browser window hosting the Test Hub. Select the Runs tab.

  3. Double-click the most recent test run to open it. You may need to refresh the data to see it.

  4. The Run summary tab provides an overview of the test run, as well as high-level details on the results of all tests included as part of the run.

  5. Select the Test results tab. This tab lists the results of each individual test case included in the run along with their results. Since there was only one test case included here, double-click it to open.

  6. You can review all details for this particular test case run from here.

  7. Scroll to the bottom to locate the iterations. Expand the first iteration.

  8. Review the results of each step in this iteration, as well as the failed login step, which shows the screenshot attached during the test run.

Task 5: Creating Shared Steps

  1. In this task, you will learn how to create shared steps. A shared step combines multiple steps that are commonly performed in sequence into a single logical step, which can be shared across tests. If the process defined by the shared steps ever changes in the future, you can update the shared step in one place and it will be reflected in all tests that reference it.

  2. Click the test case link in the Summary section.

  3. Double-click the case to open it in the test case editor.

  4. Select steps 2-4 (use Shift+Click) and click the Create shared steps button.

  5. Set the name of these shared steps to “Add Disk and Pad Combo to cart” and click Create.

  6. Now you can see the previous steps replaced with the shared steps. Double-click the shared steps to open.

  7. If necessary, you can revisit these steps later on to update them for new requirements.

  8. Press Esc to close the Shared Steps dialog.

  9. Click Save & Close to save the test case.