Start the testable app. Note that only apps installed through Jamo Automator are testable apps. The app installed by the user is not testable and cannot be used to record or replay a test case.
On the home screen of the app, tap three times with the finger on an area which is normally not reacting to the touch. The Jamo Automator menu window opens.
Select the menu ‘start recording’. The screen of the app reappears. Execute now manually the navigation of your test case. Once the manual navigation is executed, tap again three times on a place of your screen which is normally not reacting to a touch. The Jamo Automator menu reopens.
Select the first menu ‘Save test case’. A new window opens with an edit field. Type the name of the test case in the edit field and select the save entry.
Jamo Automator starts now the upload of the test case.
Go back to your browser, select the ‘Test cases’ tab. The just created test case is listed. If the test case is not yet listed, wait a few seconds and click no the ‘Refresh’ button located in the upper right corner of the form.
Click on the name of the test case. The form with the details of the test case opens. In order to change these details, click on the ‘Edit’ button in the upper right corner of the form. Edit fields appear so that the name, description, project and assigned user can be changed or specified.
Once the changes are entered, click on the ‘Done’ button in the upper right corner of the screen.
A test case can be re-used across releases of the app under test. If however the changes between affects the navigation of the test case, then a new test case specification is created in order to deal with these changes. A test case specification is thus an implementation of the test case linked to specific releases. Since this test case is just recorded, only one specification is available.
Click on the specification of the test case. The detail form of the specification opens. The fields of the specification can be changed by clicking on the ‘Edit’ button in the upper right corner of the form.
This specification has been recorded on one specific model. The view for this model is listed. If you replay this test case on another iOS device, its view will also be listed. Open the view by clicking on entry in the first column labeled ‘Mobile OS’.
In the left tree view, you have an overview of the actions that were recorded. In the right pane, there is an overview of the actions and the associated screenshots. Each recorded action is called a view step. The UI element on which the action did take place is highlighted inside the screenshot. By using these screenshots, the above test case show that the navigation is:
- Click on the search button
- Enter in the edit field the word “chicken”
- Click on the Go Button.
- Select the second chicken based recipe.
- Select the ingredients.
- Go back
- Go back
To have more details on the view step, hoover the mouse cursor over the image, the action and its arguments are displayed. To open the details a view step, click on the image of the view step or on the related entry in the left side based tree view. The detail window of the view step opens.
At the left hand side, the image of the screen on which the take will take place is displayed. On the right, the action is descripted. The action can be edited by clicking on the ‘Edit’ button in the upper right corner.
How to change and edit a view step is explained in the following sections. Now the focus is on the replay of the just recorded test case.