Manual test scripts and statements

Manual testing is a type of testing that includes human involvement and no automation.

In a typical test process, you first create test cases, and then you create the test scripts. Next, you 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 task of creating test artifacts among your group depends on the workflow of your organization. In larger organizations, several people might be involved in developing test artifacts. For example, 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 and might create the script at test-creation time.

When you construct a manual test script, use the test editor to create and edit 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.

If you set up an integration with IBM® Rational® Functional Tester, you can use the manual test script recorder option in the manual test editor to automatically capture a set of actions as steps in a manual test script. This function is also referred to as "assisted manual testing." Using the recorder to capture script steps saves your team time and eliminates user errors that might occur when you manually write manual test script steps. The manual test script recorder also gives you the option to automatically save screen captures. You can also use the manual test script recorder for exploratory testing.

You can create three types of manual testing statements:

  • Execution steps (Step) tell testers which actions to perform when they run the script. For example, "Start the application." represents an execution step.
  • Reporting steps (Reporting step) are higher-level checkpoints. Reporting steps might summarize the result of several execution steps. For example, a reporting step might ask, "Were you able to log in?"
  • Information steps(Information Step) enable testers to add notes, cautions, setup instructions, or delays between steps during test case execution. For example, “Set Voltage to 5V and temperature to 10ºC.” is an information step.
    Note: An information step is a non-verdict type of step, and does not participate in point calculation. You can configure the step type to add only a description. For details on how to enable information steps in manual test scripts, see Enabling test script preferences.

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.