iOS App Test Example

In this chapter, go through an iOS app test step by step.

Test the pre-instrumented iOS KeyPass mobile app. Your test includes the following steps:

1. Start the app on the iOS device.
2. Create a new password database.
3. Name it MyPasswords.
4. Set the password to 1234.
5. Validate that the category General exists.
6. Exit the app.

1. Create a new solution for mobile testing using the Solution wizard.
2. Open the Endpoints pad.
3. Open the recording module Recording1.rxrec.

Ranorex Studio should now look as follows:

1. Empty action table in the recording module
2. Empty repository
3. Your device is in the Endpoints pad.
4. Ranorex Service App running on the mobile device, showing the KeyPass app as instrumented.

1. Click RECORD.

2. In the device/app selection dialog, select:

   1. Your iOS device
   2. The KeyPass app
3. Click Create.
   
    

After you click Create, Ranorex Studio prepares the mobile test environment.

In Ranorex Studio

Ranorex Studio starts the selected app on your mobile device and adds the respective action in the action table.

1. The RUN button changes to reflect that it now runs the test on the current automation root, i.e., the active endpoint/mobile devices, not the computer.
2. An action that starts the app on the mobile device has been added to the action table.

On the iOS device

The instrumented KeyPass app launches on the device.

Ranorex Spy

Ranorex Spy opens in live tracking mode, showing the UI elements of the instrumented app.

1. Element browser in Spy shows all the UI elements of the instrumented app.
2. Live view of the instrumented app on the mobile device.

For mobile tests, you’ll repeatedly use this workflow:

• Capture a UI element in Spy and add it to the repository
• Create an action in the action table using that repository item (Touch / Set value / Validation)

Reference: The full workflow is explained in Create a mobile test.

Create new password database

1. Ensure that the + button is visible on the mobile device.
2. In Spy, click Refresh.
3. Drag the UI element for Empty folder from Spy to the repository in Ranorex Studio.
   
4. Drag the new repository item into the action table and create a Touch action.
   

Note: Creating this action illustrates the 2-step procedure. It remains the same for the following actions. Therefore, the following instructions don’t describe the procedure in quite as much detail.

Enter the database name

After tapping the + button, a dialog opens asking for a name and a password for the new database. To enter the name create two actions.

1. Add the name text field to your repository with Spy.
2. Create the following two actions with this repository item:

1. Touch action that places the cursor in the text field.
2. Set value action that enters the name.

Hint: If you want to test the functionality of the on-screen keyboard, you can also implement entering the name by a series of touch actions on the keys.

Enter and confirm the database password

1. Add the two text fields for the password and its confirmation to your repository with Spy.
2. Create the following four actions with these repository items:

1. Touch action and Set value action to place the cursor in the text field and enter the password.
2. Touch action and Set value action to place the cursor in the text field and repeat the password.

Confirm database creation

1. Add the Done button to your repository with Spy.
2. Create the following action with this repository item:

1. Touch action that taps the Done button to confirm database creation.

Validate the created database

Now we’ll validate whether the database was created correctly.

1. Add the file name to your repository with Spy.
2. Create the following action with this repository item:

1. Validates that the displayed file name is the same as the one entered during database creation.

Delete database and close app

1. Add the Edit, (-), and Delete buttons to your repository.
2. Create the following actions with these repository items:

1. Touch action that taps Edit.
2. Touch action that taps (-).
3. Touch action that taps Delete to confirm deletion.
4. Closes the app.

Completed recording module

If you followed the steps, your recording should now contain the full flow.

You can now switch to the test suite view and run the test. However, in a real-life scenario, the test wouldn’t be quite finished here. The next step would be to modularize the recording and structure the test suite.

The concepts of modularizing and structuring apply to all recording modules and test suites, regardless of desktop, web, or mobile tests.