Plan Manual Tests using Team Web Access
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 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. Learn more about access levels here.
For changes introduced with this version, review the Q & A section.
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.
Go to the Test hub.
If you don’t see the Test hub, you need to get full access from your TFS administrator.
Create a test plan for your current sprint.
Name the test plan. Check the area path and iteration.
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.)
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.
Add a clause to filter by the iteration path for the sprint. Run the query to display the backlog items.
Choose the backlog items that you want to test this sprint.
Now you've created a requirement-based test suite for each backlog item.
With TFS 2013 Update 3, test plans and test suites were converted to 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 Team Web Access or Microsoft Test Manager. But make sure that you set up access based on permissions for the area path.
A: Yes, 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.
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.
In MTM, open a test plan to edit the fields. The Properties tab now displays the work item form. Run settings have been moved into a new tab.
For test suites, open the test suite from the context menu to view and change fields for the work item.
A: Yes, 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.
Change the test case fields in the report by adding or removing columns from the list view of the test suite.
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 14.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 add fields, change the workflow, and customize them like any other WIT. See Modify or add a custom work item type (WIT).
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.
In this version, a test plan can be customized to have different workflow states. If you use an MTM client with a version of Visual Studio prior to Visual Studio 2013 Update 3, you might 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 or Visual Studio 2015, 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: You need to update the process configuration for the team project. See Import and export process configuration [witadmin].