Visual Studio 2017 | Visual Studio 2015 | Team Services | TFS 2017 | TFS 2015
At the start of a sprint, find out what you need to test. Discussing test cases is a great way to help the team understand the detail of what your users need. Tests planned in this way provide a clear target for the development team.
TIP You can also use the web portal to plan manual tests. It is generally more convenient for creating test cases.
Connect to a test plan if you haven't already.
The test plan links together the test cases you'll use in this sprint.
Add a manual test case to your test plan.
Name the test case.
Add the steps to perform during the test. Don't forget to include the expected results.
To add multiple lines in a step, press ALT + Enter.
Now that you've defined a manual test case, you can run it from MTM and keep the results in TFS.
Organize your test cases with test suites
Test suites are folders inside a test plan that help you organize tests. When you run tests, you can choose to run all the tests in a suite, one after another.
Create a new test suite.
Select a suite and then create new tests in the suite.
Drag test cases from one suite to another, or cut and paste.
CTRL + drag or copy and paste to make the same test case appear in more than one suite.
These operations don't affect the test case itself. Suites contain links to test cases, and it's the links that you're moving or copying. For the same reason, removing a test case from a suite doesn't delete the test case from TFS.
Try this next
Or, dig deeper:
Help and support
Submit bugs through Connect, make suggestions on Uservoice, and send quick thoughts using the Send-a-Smile link in the Visual Studio, Team Services, or TFS title bar. We look forward to your feedback.