How do I series: Planning manual tests using the web portal

Hi folks,

in this post I will show you how you can plan for your manual tests using TFS web portal client.

The way you can see when the testing for a specific sprint or milestone is complete. you have to create test plans to track manual testing for sprints or milestones.

With Team Foundation Server, you can customize test plans and suites. For example, add an extra field to identify the reviewer for a test plan, or change the default values for the state field to fit your process better.

To use these features, you’ll need Advanced level access.

  1. Connect to your team project and then open the web portal from Team Explorer.

  2. Use Team Web Access to plan your tests

    Or simply open the web portal directly from your browser. For example, to connect to the server named FabrikamPrime use: http://FabrikamPrime:8080/tfs/, then you can select your team project.

  3. Go to the Test hub.

    Choose the test hub from Team Web Access

    If you don’t see the Test hub, you need to get full access from your TFS administrator.

  4. Create a test plan for your current sprint.

    New button in the test plan explorer pane
  5. Name the test plan. Check the area path and iteration.

    Create button in the create test plan dialog box
  6. Now add test suites for the backlog items that need manual tests. (These backlog items could be user stories, requirements or another work item based on the setup of your team project.)

    New button in the test plan explorer pane

    You use requirement-based suites to group your test cases together so you can track the testing status of a backlog item. Each test case that you add to a requirement-based test suite is automatically linked to the backlog item.

  7. Add a clause to filter by the iteration path for the sprint. Run the query to display the backlog items.

    Add new clause button to update the query.
  8. Choose the backlog items that you want to test this sprint.

    Select items from the list. Then create suites.

    Now you’ve created a requirement-based test suite for each backlog item.