Run an Exploratory Test in Sprinter

Relevant for Power Mode only

The following steps describe how to run an exploratory test in Sprinter.

This task includes the following steps:

1. Prepare the exploratory test

   • If you are using ALM or Octane, open a test in Sprinter, as described in Run a Manual Test in Sprinter.

   • If you are not using ALM, open a test in Sprinter, as described in Run a Manual Test in Sprinter.

   • Turn on Power Mode and select an application for your test, as described in the Run a Manual Test in Sprinter step.

2. Explore your application

   Begin the run session, and perform any user action in your application. Sprinter captures all of the user actions that you perform. You can manage the capturing of user actions and view the status of your exploratory run in the Run Control Sidebar. For example, you can pause the capturing of user actions temporarily, and resume the capturing when it is relevant.

   For details, see Run Control Sidebar.

3. Review and export the captured user actions

   At the end of the run session, review the captured user actions in the User Actions pane of the Run Results View. For user interface details, see User Actions Pane/User Actions Summary Dialog Box.

   In this pane you can export the captured user actions to:

   • a new manual test with steps (for ALM users). In the new test, each user action is converted to a manual step. Before saving the new test to Application Lifecycle Management, you can edit its details, steps, and any user-defined information that your Application Lifecycle Management project requires. For details, see Generate Test Area.

   • a new local test with steps (for non-ALM users). In the new test, each user action is converted to a step. Before saving your test, you can edit its details. For details, see Generate Test Area.

   • a Unified Functional Testing-compatible automated test data file. This XML file contains all the user actions and test object representations of the controls in your application that you used during the run session. You can then import this file to UFT One, where it is converted to a GUI test with a local object repository.

   • an Excel or CSV file. This file contains all the user actions that you performed during the run session. You can edit the content of the file and then import it into an existing test or component.