In a typical process, you first create test cases, and then you create the test scripts. The next step is to associate the test scripts with the test cases. During test execution, the script opens and guides the tester through the test step-by-step.
They way you divide the creation of test artifacts among your group depends on the work flow of your organization. In larger organizations, several people might be involved in developing test artifacts. It might make sense for one team member to create the scripts, while another team member creates the test cases. In smaller organizations, one person might fill several roles, so that person might create the script at test-creation time.
When constructing a manual test script, use the test editor for creating and editing test scripts. Type statements into the editor and assign a type to each step. You can also create manual test scripts automatically in the Test Case Design section of a test case.
You can create two types of manual testing statements:
) tell the tester
what actions to perform when running the script. For example, "Start
the application." represents an execution step.
) are higher-level checkpoints that are often included
in reports. Reporting steps might summarize the result of several
execution steps; for example, a reporting step might ask, "Were you
able to log in?"You can attach images, files, comments, and verification text to a statement. Attachments are accessible during the test run. In addition, you can insert keywords and test data.