Create manual test cases to check that each of the deliverables meet your users' needs. Organize your test cases by adding test cases to test suites. Then choose which testers you want to run the tests.
If you haven't already, create a test plan and requirement-based test suites.
Choose a requirement-based test suite, and then create a test case for that suite.
A requirement-based test suite is created from a backlog item. If you add a test case to this type of suite, it is automatically linked to that backlog item.
Add test steps with actions and expected results so that any team member can run the test. You can add attachments to a step if you want.
Now you have created a test case that you can run.
You can assign test cases to be run by a different tester. Select the tests that you want to reassign. Then choose the tester who you want to run the tests.
Or you can assign all the test cases in a test suite to be run by multiple testers. This is useful for acceptance testing.
After you select the testers, you can email the testers to let them know that the tests are ready to be run. (A user only needs a Basic license to run tests from Visual Studio Online.)
Q:Can I add an extra line into a test step?
A:Yes. Press Shift+Enter in the action or expected results field to add an extra line.
Q:How do I insert a test step into a test case?
A:Select a test step. Press Alt+P to insert a test step above the selected step.
Q:Is there a way to quickly add multiple test cases at the same time?
A:Yes. Use the grid view when you add test cases to the test suite.
In the grid view, use the context menu to insert, clear or delete a row.
Q:Can I bulk edit multiple test cases?
A:Yes. Switch the view from list to grid. All the test cases for the current test suite will be displayed in the grid with their test steps. This is a helpful view if you want to review your test cases with other team members jointly. When you review, you can update and add new test cases.
Or you can filter and sort the test cases. Then select only the ones that you want to bulk edit.
To return to the test suite view, switch the view from grid back to list.
Q:Can I copy test cases and test steps from an existing Excel worksheet?
A:Yes. Copy the columns from Excel that you want to use for the title, action and expected results fields. Any formatting in the columns, other than multiline, will not be copied into the worksheet. Paste these columns into the grid view, edit if necessary, and save them. (This is only supported with Internet Explorer and Chrome browsers.)
Q:Can I copy test cases from the grid view to an Excel worksheet?
A:Yes. Copy the data and paste it into your Excel worksheet. Any formatting in the test steps, other than multiline, will not be copied into the worksheet. (This is only supported with Internet Explorer and Chrome browsers.)
Q:Can I edit other fields in the grid view?
A:Yes. Use column options to select fields in the test case work item.
The fields can then be viewed and edited when you switch to the grid view.
Q:Can I tag test cases so that I can view only tests with specific tags?
A:Yes. Tag test cases in a suite with any tag that is important to you. For example, tag all the tests related to login so that you can rerun these tests if a bug is fixed for the login page. Then you can filter on that tag from the test hub. You can add and edit tags when you edit a test case, or bulk edit tags in the grid view.
You can also create query-based suites using tags.
Q:Can I share test steps between test cases?
A:Yes. Choose the steps that you want to share. More details are here.
Q:Can I add parameters to a test case to run multiple times with different data?
A:Yes. Choose a test step and then add the parameter. More details are here.
Q:Can I share the data for parameters between test cases?
A:Yes. That way test cases that use the same parameters can be run with the same data for consistent results. Convert existing parameters to shared parameters.
After you have created a shared parameter set, open another test case and add the shared parameter set to that test case. More details are here.
Add, edit and rename your shared parameter sets from the parameters tab. View the test cases that reference them in the test cases pane.
Each shared parameter set is a work item. From the Properties tab, you can view or make changes to this work item. For example, you can assign owners and track changes.
Q:Can I import parameter values from an Excel spreadsheet to my shared parameter sets?
A:Yes. Copy the data from your Excel spreadsheet and paste it into your shared parameters grid. You can also copy the data from your grid back into Excel if you need to.
Q:How can I find out if a test case has been added to other test suites?
A:Select a test case, then choose to view the test suites details. The associated test suites pane shows you any test suite for any test plan that contains this test case. This includes all team projects. Click the test suite to view it. Hover over the test suite in the pane to view the team project and the test plan for that test suite.
Q:What happens when I delete a test case from a requirement-based test suite?
A:The test case still exists in your team project, but the test case is removed from the test suite. In addition, it is no longer linked to the backlog item for that test suite.
Q:Why do I see the wrong test suite and tests when I click 'View Tests' from the notification email about tests that are assigned to me?
A:This may happen if you were prompted to enter login credentials for Visual Studio Online when you clicked this link. Without logging out from Visual Studio Online, click 'View Tests' again to see the correct test suite and tests.