Create manual test cases

Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018

Create manual test cases to check that each deliverable meets your users' needs. Manual test cases define individual steps testers perform, including steps that are shared across test cases. To test different data, you specify parameters for the test steps. To learn more, see Share steps between test cases and Repeat a test with different data. For an overview of test artifacts, see Test objects and terms.

Organize your test cases by adding them to test plans and test suites. Then assign testers to run the tests.

For an overview of test artifacts, see Test objects and terms.

Note

Test iterations are designed to support data-driven scenarios, not workflow-driven scenarios. From a best practice perspective, if you have two test scenarios where the workflows are different, consider creating separate test cases. Also see FAQs for manual testing.

Prerequisites

  • You must connect to a project. If you don't have a project yet, create one.

  • You must be added to a project. To get added, Add users to a project or team.

  • To view test-related work items, you must have Basic access or higher and permissions to view work items under the corresponding Area Path.

  • To add test plans and test suites, manual test cases, delete test artifacts, and define test configurations you must have Basic + Test Plans access level or have one of the following Visual Studio subscriptions:

  • To add or edit test-related artifacts, you must have the following permissions:

    • To add or modify test plans, test suites, test cases, or other test-based work item types, you must have 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, you must have 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, change test configurations associated with test suites, and modify a test suite hierarchy (move a test suite), you must have Manage test suites permission set to Allow under the corresponding Area Path.

To learn more, see Manual test access and permissions.

Note

If you're new to using Azure Test Plans, review Navigate Test Plans to understand how to use the user interface to access select functions.

Create test cases

  1. If you haven't already, create a test plan and requirement-based test suites.

  2. Select a requirement-based test suite. To the right, select the New Test Case button.

    Screenshot shows test cases with New Test Case button highlighted.

    If you have no existing test cases, the button appears in the lower right.

    Note

    The test suite shown here was created from a User Story work item in the team's backlog board. When you add a test case to this kind of suite, the test case is automatically linked to the backlog item. To create test cases this way, open the context menu for the work item and choose Add test.

  3. In the new work item, enter a title. Select the Click or type here to add a step option.

    Screenshot shows the steps entered for a test case.

    Add test steps with a description of the action required to carry out the test and the expected results so that any team member can run the test. You can add attachments to a step if you want. Repeat until you have added all the steps for the test.

    Note

    You can share steps between test cases. For more information, see Share steps.

    Now you've created a test case that you can run.

You can also copy test cases. For more information, see Copy or clone stories, issues and other work items.

Assign configurations to test cases

You can specify configurations, such as different operating systems, web browsers, and other variations for your tests.

To assign test configurations to all test cases in a test suite, select the test suite, select More options or right-click to open the context menu, and then select Assign configurations.

In the Assign configurations to test suite dialog box, select the configurations you want.

Screenshot shows the Assign configurations to test suite dialog box with some options selected.

You can also assign configurations to individual test cases. Select one or more test cases, select More options or right-click to open the context menu, and then select Assign configuration.

The Assign configurations to selected test cases dialog box opens. Make and save your changes.

For more information about configurations, see Test different configurations.

Reorder test cases

You can reorder manual test cases in static suites, requirement-based suites, and query-based suites. Open a test case, then use the up and down arrows to change the order.

Screenshot showing the arrows used to move test steps up or down.

There are also options to change order in the step context menu.

Add existing test cases to a test suite

You can add existing test cases to a test suite.

  1. Select a test suite. From the New Test Case menu, select Add existing test case.

    Screenshot shows the Add existing test cases option to select.

  2. In the Add test cases to suite dialog box, add search clauses, as needed, and then select Run query.

    Screenshot shows the Add test cases to suite dialog box with the Run query button highlighted.

  3. After you find the test cases you want, select Add test cases.

  1. If you haven't already, create a test plan and requirement-based test suites.

  2. Select a requirement-based test suite. In the right-hand pane, choose + (New) and then choose New test case.

    Select the test suite for a backlog item and adding a new test case

    The test suite shown here was created from a User Story work item in the team's backlog board. When you add a test case to this kind of suite, the test case is automatically linked to the backlog item. To create test cases this way, open the shortcut menu for the work item and choose Add test.

  3. Choose the Click or type here to add a step link and add test steps with a description of the action required to carry out the test and the expected results so that any team member can run the test. You can add attachments to a step if you want. Repeat until you have added all the steps for the test. Now you've created a test case that you can run.

    Creating the steps for a new manual test case

    You can share steps between test cases. For more information, see Share steps.

    How can I find an existing test case within a test plan?

You can reorder manual test cases in static suites, requirement-based suites, and query-based suites. Choose Order tests on the tool bar, then drag and drop one or more tests. Or open the shortcut menu for a test to move it to the top or to another position. After reordering the tests, you can sort them by the Order field and then run them in that order with the web runner.

Order test cases

Tip

You can create a test case that automatically links to a requirement—User Story (Agile), Product Backlog Item (Scrum), Requirement (CMMI), or Issue (Basic)—when you create a test from the Kanban board. To learn more, see Add, run, and update inline tests.

Use the Grid view to edit test cases

You can copy and paste test cases into the Grid view.

To open the Grid view, select the Grid View icon at the right.

Screenshot shows the Grid View button used to open the Grid view.

Instead, you can select several test cases and open them for editing in the Grid view. In the context menu, select Edit test case(s) in grid.

Screenshot shows several test cases selected with the context menu open and Edit test case(s) in grid selected.

On the Grid context menu, you can add, delete, or clear rows.

Screenshot shows the Grid context menu to insert, delete, or clear rows.

You can use the Grid view when you add multiple test cases to the test suite:

Screenshot shows option to add test cases using the Grid view.

You can edit other fields in the Grid view. In the List view, use the column options to select the fields in the test case work item.

Screenshot shows the Column Options button.

You can then view and edit these fields when you switch to the Grid view.

Switch between Grid and List views using the View menu at the right of the window.

Use the View menu to switch between List and Grid views.

On the grid shortcut menu, you can add, delete, or clear rows.

Use the grid's shortcut menu to insert, delete, or clear rows.

You can use the Grid View when you add multiple test cases to the test suite:

Create new test cases using the grid.

Note

Do not use the Teams plugin for Excel to add or update test case work items. Excel cannot parse the format used to store test steps, and in some cases this may affect the formatting of the test case work items.

You can edit other fields in the Grid view. In the List view, use the column options to select the fields in the test case work item.

Use column options to select fields to edit

You can then view and edit these fields when you switch to the Grid view.

Use Excel to copy test case information into a Grid view

You can copy test cases and test steps from an existing Excel worksheet. Copy the columns from Excel that you want to use for the title, action, and expected results fields. Copying does not copy column formatting, other than multiline, from the worksheet. Paste these columns into the Grid view, edit if necessary, and save them.

Screenshot shows the save option for steps copied from Excel to the Grid view.

You can copy the data from the Grid view and paste it into your Excel worksheet. Copying does not copy test step formatting, other than multiline, into the worksheet.

Note

Do not use the Teams plugin for Excel to add or update test case work items. Excel cannot parse the format used to store test steps, and in some cases this may affect the formatting of the test case work items.

You can copy test cases and test steps from an existing Excel worksheet. This is supported only with Internet Explorer and Chrome browsers.

Copy the columns from Excel that you want to use for the title, action, and expected results fields. Copying does not copy column formatting, other than multiline, from the worksheet. Paste these columns into the Grid view, edit if necessary, and save them.

Save copied test cases in grid view

You can copy the data from the Grid view and paste it into your Excel worksheet. Copying does not copy test step formatting, other than multiline, into the worksheet.

Assign testers

You can reassign test cases so that a different tester can run them. You can assign all the test cases in a test suite to multiple testers, which is useful for acceptance testing.

Testers need Basic access to run tests from Azure Test Plans.

  1. In the context menu for a test suite, select Assign testers to run all tests.

    Screenshot shows the Assign testers to run all tests option in a test suite context menu.

    The Select testers to run all the tests in suite dialog box opens.

  2. Add or remove testers from the list. After you select the testers, select Send email and edit the message as required so they know that tests are ready for them to run.

    Screenshot shows Assigning testers to run all tests dialog box with Search users and Send email called out.

    The email contains a link that testers can open to see the list of assigned tests.

You can assign an individual test case to a tester.

  1. In the Execute tab for a test suite, select a test, and then open the context menu.

    Screenshot shows the context menu for a test case with the Assign tester option selected.

  2. Select Assign tester. Search for and select a tester.

  1. You can reassign test cases so that another tester can run them. Select the tests that you want to reassign. Then open the shortcut menu (choose the "..." ellipses or right-click) and select the tester you want to run the tests.

    Reassigning tests to a different tester

    Or, you can assign all the test cases in a test suite to multiple testers. This is useful for acceptance testing. Open the shortcut menu for the test plan and choose Assign testers to run all tests.

    Assigning testers to run all tests

  2. Add or remove testers from the list. After you select the testers, tick the Send email checkbox and edit the message as required so they know that tests are ready for them to run.

    Send emails to testers

    The email contains a link that testers can open to see the list of assigned tests. Testers need just Basic access to run tests from Azure Test Plans.

Manage test cases

You can open a test case to view it or edit it. To open a test case in a test suite, in the Define tab, double-select the name of the test case to open. In the Execute tab, select a test case, open its context menu, and select Edit test case.

Screenshot show the Edit test case option for a test case in the context menu

A test case can be linked to test suites, requirements, and bugs. To see linked items, in the Define tab, open the context menu for a test case, and select View Linked Items.

Screenshot shows the Linked Items dialog box for a test case with options to view Test Suites, Requirements, and Bugs.

In the Linked Items dialog box, you can view Test Suites, Requirements, and Bugs.

Bulk edit test cases

You can edit more than one test case at a time. Select several test cases in a test suite and select Edit test case(s).

Screenshot shows the Edit work items dialog box where you can select fields and values for several test cases.

Select a Field and enter a Value. Select Add new field to add another field-value pair.

Use tags for test cases

You can tag test cases and view only the ones with specific tags. For example, tag all the tests related to signing in so that you can rerun these tests if a bug is fixed for that page. You can filter on that tag from the Test Plans web portal.

To add new tags to add to work items, you must have Basic access or higher and have the project-level Create new tag definition permissions set to Allow. for more information, see Add work item tags.

You can add and edit tags when you edit a test case, or bulk edit tags in the Grid view. You can also create suites based on queries when you use tags.

Screenshot shows tags for a test case.

Rename or remove test cases

You can rename or remove test cases. Open the test case from its context menu.

Screenshot shows a test case with its context menu with Open test case selected.

Here you can rename the test case.

Screenshot shows a test case with its name selected to edit.

Or you can remove the test case from the test suite. From the context menu for the test case, select Remove.

Remove a test case.

To permanently delete test plans and test suites, you must be a member of the Project Administrators group or have the Area Path node-level Manage test plans or Manage test suites permission set to Allow. To manage or delete test artifacts, you must also have your access level set to Basic + Test Plans or Visual Studio Enterprise. For more information, see Delete test artifacts in Azure Boards.

You can tag test cases and view test cases only with specific tags. For example, tag all the tests related to signing in so that you can rerun these tests if a bug is fixed for that page. Then you can filter on that tag from the Test Plans web portal.

To add new tags to add to work items, you must have Basic access or higher and have the project-level Create new tag definition permissions set to Allow. for more information, see Add work item tags.

You can add and edit tags when you edit a test case, or bulk edit tags in the grid view. You can also create suites based on queries when you use tags.

In the Test Plans web portal, on the Test Plans page, choose or add tags from the test case pane

You can rename or delete test cases. Open the test case from its shortcut menu.

Open a test case for editing

Here you can rename the test case.

Rename a test case

Or you can permanently delete the test case.

Delete a test case

To delete test plans and test suites, you must be a member of the Project Administrators group or have the Area Path node-level Manage test plans or Manage test suites permission set to Allow. To manage or delete test artifacts, you must also have your access level set to Basic + Test Plans or Visual Studio Enterprise.

To delete test plans and test suites, you must be a member of the Project Administrators group or have the Area Path node-level Manage test plans or Manage test suites permission set to Allow. To manage or delete test artifacts, you must also have your access level set to Basic + Test Plans or Visual Studio Enterprise. For more information, see Delete test artifacts in Azure Boards.

Next step