Purpose
  • To execute performance test.
  • To review test results.
  • To investigate and organize test results for evaluation.
  • To log defects.
Steps
Input Artifacts: Resulting Artifacts:
Worker: Performance Tester

Execute Test Procedures To top of page

Purpose
  • To execute the test procedures (or test scripts if testing is automated)
Tool Mentors:

To execute the tests, the following steps should be followed:

  • Set-up the test environment to ensure that all the needed components (hardware, software, tools, data, etc.) have been implemented and are in the test environment.
  • Initialize the test environment to ensure all components are in the correct initial state for the start of testing.
  • Execute the test procedures.

Note:  executing the test procedures will vary dependent upon whether testing is automated or manual.

  • Automated testing:  The test scripts created during the Implement Test activity are executed.
  • Manual execution:  The structured test procedures developed during the Design Test activity are used to manually execute test.

Evaluate Execution of Test To top of page

Purpose
  • To determine whether the tests completed successfully and as desired
  • To determine if corrective action is required
Tool Mentors:

The execution of testing ends or terminates in one of two conditions:

  • Normal:  all the test procedures (or scripts) execute as intended.
  • Abnormal or premature:  testing was halted and complete test coverage was not achieved.

If testing terminates normally, continue with Verify Test Results.

If testing terminates abnormally, continue with Recover From Halted Tests.

Recover From Halted Tests To top of page

Purpose
  • To determine the appropriate corrective action to recover from a halted test
  • To correct the problem, recover, and re-execute the tests
Tool Mentors:

There are two major types of halted tests:

  • Fatal errors - the system fails (network failures, hardware crashes, etc.)
  • Test Script Command Failures - specific to automated testing, this is when a test script cannot execute a command (or line of code).

Both types of abnormal termination to testing may exhibit the same symptoms:

  • many unexpected actions, windows, or events occur while the test script is executing
  • test environment appears unresponsive or in an undesirable state (such as hung or crashed).

To recover from halted tests, do the following:

  • determine the actual cause of the problem
  • correct the problem
  • re-set-up test environment
  • re-initialize test environment
  • re-execute tests

Verify Test Results To top of page

Purpose
  • To determine if the results are within the expected range
Tool Mentors:

Following the completion of testing, the results should be reviewed to determine if they are consistent with the expected results.

If all the results are consistent, then continue with Log Defects.

If the results are inconsistent, then Investigate Unexpected Results.

Investigate Unexpected Results To top of page

Purpose
  • To identify appropriate action when actual results differ from expected
Tool Mentors:

Test failures and unexpected results should be investigated to determine if they are legitimate defects or are the result of external  influences (to the target of test), such as an unexpected condition in the test system or the test script.

The most common failures / unexpected results include:

  • Test verification failures - this occurs when the actual result and the expected result do not match.
  • Unexpected windows - this occurs for several reasons. The most common is when a window other than the expected one is active or the number of displayed windows is greater than expected.
  • Missing windows - this failure is noted when a window is expected to be available (but not necessarily active) and is not.

The corrective action for unexpected results include:

  • Determine why the expected and actual results vary.
  • Ensure that the test verification methods focus only on the essential items and / or properties.
  • Ensure the test scripts and target for test are synchronized.
  • Ensure there are no new windows were added (or deleted from) to the GUI.

If the unexpected result is due to an error identified in the test scripts, or due to a problem with the test environment, the appropriate corrective action should be taken.   See "Recover From Halted Tests" above.

If the unexpected result is due to another source, continue with Log Defects.

Log Defects To top of page

Purpose
  • To enter defect information into a tracking tool to initiate corrective action
  • To initiate defect tracking and defect management
Tool Mentors:

For all unexpected results (due to sources other than test scripts or resolved problems with the test execution) defects should be generated. The information should be accurate, appropriate, and meet accepted defect tracking standards or guidelines.

Display Rational Unified Process using frames

 

© Rational Software Corporation 1998 Rational Unified Process 5.1 (build 43)