Run tests in Power Mode

Before you run a manual test in Sprinter, you need to decide if you need to run your test in Power Mode .

To activate Power Mode, toggle the switch on the top right banner.

In this topic:

Power Mode benefits

When you run a Sprinter test in Power Mode, Sprinter is able to learn your application's display and identify its objects.

With this information, Sprinter can:

• Create and run macros to allow Sprinter to perform a set of actions in your application for you.

• Automatically inject data into fields in your application (for ALM, ALM Octane, and UFT One users).

• Replicate your user actions on multiple machines (for ALM, ALM Octane, and UFT One users).

• Scan the application for potential defects (for ALM, ALM Octane, and UFT One users).

• Keep a record of your user actions. Add comments and reminders to the recorded user actions in your run, for later review.

• Keep a record of the defects you submitted for each action.

• Automatically include the list of your steps or user actions in any defect you submit to create a defect scenario.

When you are in Power Mode, Sprinter keeps a record of all your user actions, which you can view as a list or in the Storyboard at the end of your run. You can also include the list of your steps or user actions in any defect you submit to let Sprinter automatically create a defect scenario for you.

You can export the list of user actions at the end of your run to an Excel spreadsheet, modify them for use as steps, and then import them to a test in the future. You can also export the list of your steps at the end of your run to a Sprinter data file and import them to UFT One.

After a test run, you can use the test steps as a template and automatically generate a test. For details, see the Generate Test area.

For ALM or UFT One users, Sprinter's built-in scanners let you scan your application for spelling errors, Web Standards errors, broken links, or localization errors.

For ALM and UFT One users, when you run a test in Power Mode, you can accomplish the following tasks:

• Inject data into your application

• Scan applications for potential defects

Back to top

Power Mode features

The following table summarizes the Power Mode features to help you decide if you need to run your test in Power Mode:

Feature	Description
Application	You must define an application for your test to use Power Mode. Defining an application for your test also enables Sprinter to install, uninstall, or restart the application automatically when you start your test. Sprinter saves settings and other user-specific configurations and applies this information the next time you run Sprinter. Many Power Mode configurations are associated with their specific application. Once you define the application for your test, all tests with the same defined application will share the same Power Mode configuration. For details, see: Applications How user information is stored Applications tab (Power Mode)
Data injection	Enables you to automatically enter data into fields in your application. For details, see Data Injection. Note: This feature is only available if you log in using ALM or a UFT license.
Macros	Enables you to record a series of user actions that you can run as a single command during your run. For details, see  .
Scanners	Enables you to check that various aspects of your application behave correctly during a run session. You can scan your application for spelling errors, broken links (Web applications only), Web Standards errors (Web applications only), and localization errors. For details, see Sprinter scanners. Note: This feature is only available if you log in using ALM or a UFT license.
Storyboard	Enables you to view a timeline of the user actions you performed on your test. The Storyboard displays the defects, comments, and defect reminders for each action in your test. For details, see Storyboard window.
Comments	Enables you to add comments to user actions in your run. These comments can be reviewed later in the Storyboard window.
User Actions summary	Enables you to view a summary of the user actions in your test. For details, see User Actions Pane/User Actions Summary dialog box.

Back to top