Plan Manual Tests

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

With TFS 2013 Update 3, 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. This upgrade to Update 3 converts test plans and test suites into work items. This changes the IDs. Any bookmarks that you had to take you directly to a test plan or a test suite will no longer work because the IDs have changed. You still access test plans and suites using either the Team Web Access or Microsoft Test Manager. But make sure that you set up access based on permissions for the area path.

For additional changes introduced with TFS 2013.3, review the Q & A section.

  1. If you haven't already, create your team project and create your backlog.

  2. Connect to your team project and then open Team Web Access from Team Explorer.

    Use Team Web Access to plan your tests

    Or simply open Team Web Access 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.

A: If you are using on-premises TFS with TFS 2013 Update 3, you can edit the properties of test plans and test suites from Team Web Access or Microsoft Test Manager (MTM).

From the Test hub in Team Web Access, select a test plan or test suite and then open it.

From the Test Hub, click Open Test Plan

In the work item form, you can view and change any custom fields, status, summary, details, attachments, and links for your test plan or your test suite.

With Update 3 for MTM and TFS 2013 Update 3 installed: You can edit the properties of the work item from MTM too. Open a test plan to edit the fields. The Properties tab now displays the work item form and run settings have been moved into a new tab.

Select test plan and choose the Properties tab

For test suites, open the test suite from the context menu to view and change fields for the work item.

When only TFS 2013 Update 3 is installed: Use the test plan id or test suite id to open the work item directly in MTM to edit the properties of a test plan or test suite. Open the test plan or test suite to find the id and then press Ctrl+g to go to that specific work item from MTM.

When TFS 2013 Update 3 is not installed: You can only open a test plan or a test suite from Microsoft Test Manager and not Team Web Access. Your test plans and test suites are not work items. To open a test plan in MTM directly from Team Web Access, you must install Visual Studio 2012 Update 3 or later. (The most recently installed version of MTM is launched.)

Open test plan using Microsoft Test Manager

A: Yes. With TFS 2013.3, work item history tracks changes to test plans and test suites. For example, adding tests to a test suite or changing configurations are tracked. In the work item form, under History, choose ALL CHANGES to view the audit trail.

View audit trial in test plans and test suites

A: Static test suites can contain any test case that you want. Or, they can contain other test suites—just like folders. Add a static test suite from the Test Plan tab with the context menu or the plus icon on the toolbar.

A: Yes. You can create a static test suite to do this. Drag test suites to group them in a static test plan.

Use static test suites like folders

A: Use a query to group together test cases that have a particular characteristic - for example, all the tests that have Priority=1. The suite will automatically include every test case that is returned by the query that you define.

A: Yes. If you have installed Team Foundation Server 2013 Update 2 or later, you can export test plans, test suites and test cases using Team Web Access. You can select the detail that you want in the report. You can then email or print this report for review.

Choose a test suite, right-click and choose Export

Change the test case fields in the report by adding or removing columns from the list view of the test suite.

A: Yes. Choose the Print option from the Export dialog box, then choose Cancel from the Print dialog box. The data for the report is displayed. Select all the text, then you can copy and paste it into a Microsoft Word document if you want. All the formatting in the report is retained.

A: Yes. For example, you can edit the XSLT file to add a company logo or change the format of the data. Make a backup copy of this file before you edit it. These changes will apply when any user exports data from a test plan. The XSLT file is on the TFS server in this location:

C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services\_tfs_resources\TestManagement\v1.0\Transforms\1033\TestSuite.xsl

Keep a copy of any changes you make to this file, because this file could be overwritten if you install a Team Foundation Server update.

This location might be different, based on the installation path for TFS and the locale: <installation path>\Application Tier\Web Services\_tfs_resources\TestManagement\v1.0\Transforms\<locale>\TestSuite.xsl.

A: You can connect and use MTM. But the test plans and test suites have not been upgraded to be work items, so you cannot access the work item properties.

A: You can add fields, change the workflow, and customize them like any other WIT. See Modify or add a custom work item type (WIT).

A: With TFS 2013 Update 3, you can customize test suite states, so we’ve removed the restriction to only let you run tests if the test suite state is “In Progress”. Some users may have their own custom states that they want to use for tests that can be run. So this change allows more flexibility for our users.

A: Prior to TFS 2013 Update 3, test plans could only have “Active” and “Inactive” states and test suites could only have “In Planning”, “In Progress” and “Completed” states. With Update 3, a test plan can be customized to have different workflow states. If you use an MTM client with an earlier version (prior to Visual Studio 2013 Update 3), you may get an error when you try to update the state because this version of the client was not designed for custom states. Upgrade your MTM client to Visual Studio 2013 Update 3 and you will be able to change the states. Or you can open the test plan or test suite work item directly from MTM (type Ctrl+g, then enter the id of the work item).

A: With TFS 2013 Update 3, you can add custom states to test plans based on your workflow. Some users may choose to use a different state to represent an active or inactive state. Now we need to show all test plans whatever the value of the state.

A: Open the test suite and change the state in the work item form.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft