To work with Power Mode features, you must define the application you will be testing. This enables Power Mode to run advanced features such as data injection and macros on your application.

Many Power Mode configurations are associated with their specific application.

Because you define an application for your test, all tests with the same defined application will share the same Power Mode configuration. This saves you the time of redefining these configurations for each one of your tests.

You can also define applications in Plan mode, when creating new tests or components. For details, see Select Application Dialog Box.

Example: Suppose you are testing a banking mobile application. You create a test and define your application with the name My_Banking_App. During your test you then record a macro on the login page and save it with the name Login_Macro. Sprinter remembers that the Login_Macro macro was recorded for the My_Banking_App application.

In the future, whenever you run a test with My_Banking_App defined as its application, the Login_Macro macro will be available for your test.

The following information is associated with the application in your test:

  • Data injection data sets (for ALM and UFT users)

  • Macros

  • Rules (for use with mirroring - for ALM and UFT users)

When you define an application, you provide Sprinter with a logical name for the application. Power Mode associates your information with this logical name. This logical name is displayed next to the Application node in the Power Mode Group and in the Application Pane (Power Mode Group).

You may want to create more than one version of an application with different logical names, and associate specific information with each version.

Example: Suppose you are testing a banking mobile application that has multiple versions for different languages. Each version of the actual application is named Banking. You can define multiple mobile banking applications for your tests, and give each one a meaningful, logical name such as Banking_Spanish and Banking_French.

You can then associate different information with each version of the mobile application. For example, you can associate Spanish data sets with the Banking_Spanish application and French data sets with the Banking_French application.

Whenever you run a test with Banking_Spanish as the defined mobile application, the Spanish data sets will be available. Whenever you run a test with Banking_French as the defined mobile application, the French data sets will be available.

For details on how to configure Power Mode features, see Prepare a Test to Run in Power Mode.

For more details on how Sprinter maintains application information and which features are associated with the defined application, see How User Information is Maintained.