Testing Use Cases

Software testing may be thought of as having two modes of execution:

  1. Formal testing, where the users are actively working through a test plan and expect to find issues.

  2. Ad-hoc testing, where users are concentrating on using the software rather than testing the software, e.g. beta testing.

The Test Evidence Suite may be used in either case and demonstrates advantages over more traditional ways of working.

Formal Testing

Test Recorder removes the need to perform manual screen captures during test execution.

Test Recorder acts as an extension to your usual test execution process.

When working through a set of test cases you can either:

  1. Add a note at the start / end of each test case to create one large recording.

  2. Start / stop the recorder to create a recording for each test case.

Experience shows that around ten minutes of recording is optimal for review.

../_images/formalprocess.jpg

Ad-hoc Testing

Ad-hoc testing utilises the black box aspect of Test Evidence.

Start the Test Recorder and forget it exists until something goes wrong.

If there’s an error then stop the recorder, add text annotation if required and send the .tra file for analysis.

../_images/adhocprocess.jpg