In a typical process, you first create test cases and then to create 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.
How you divide the creation of test artifacts among your group depends on the work flow of your organization. In larger organizations, several people may 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 may 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 statement.
You can create three 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.
) ask questions about the application that you are testing.
For example, "Did the User Login window open?" asks the tester to verify specific
window activity.
) are higher-level verification points. They also ask questions,
but their answers require higher visibility and often are included in reports.
Reporting steps might summarize the result of several verification points;
for example, a reporting step might ask, "Were you able to log in?"You can also attach images, text files, comments, and verification text to a statement. Attachments are accessible during the test run.