Planning manual tests using the web portal
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 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.
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 the web portal 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 the web portal or Microsoft Test Manager (MTM).
From the Test hub in the web portal, 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, 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.
A: A static test suite can contain a combination of test cases and test suites as children. Add a static test suite from the Test Plan tab with the context menu or the plus icon on the toolbar. Simply choose the test cases that you want to add to this static test suite, or add another test suite.
A: Yes, you can create a static test suite to do this. Drag test suites to group them in a static test plan.
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, you can export test plans, test suites and test cases using the web portal. 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. 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 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 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.
A: In this version, 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 might have their own custom states that they want to use for tests that can be run, so this change allows more flexibility.
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: In this version, you can add custom states to test plans based on your workflow. Some users might 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.
Q: When I connect to TFS 2015 from an MTM client using Visual Studio 2013.2 (or earlier versions) I get an error. How do I fix it?
A: You need to update the process configuration for the team project. See Import and export process configuration.
A: Go here.
A: Get started using MTM here.
Now create your manual test cases.
Explore your app without planning in advance.