Step 3: Record a new test case on Android

Record a new test case on Android

Start the app under test by touching the icon of the launcher app. The first window of the app opens.

Touch the Jamo button. Since this is the first time that you access the Jamo Automator functionality, the tool will ask you to login again. Once that you are logged in, the ‘Jamo Action’ dialog box is displayed. Touch the ‘Start recording’ button in order to create a test case.

Execute now manually the test case. The tool will record all the actions. Once the end point of the test case is reached, touch again the Jamo button. Select the button: ‘Stop and save recording’.

step3 image1

Enter in the new form the name of the test case and press the upload button.

step3 image 2

During upload, the title of the dialog box changes into ‘Uploading <your test case name>’.

step3 image 3

It might take several seconds to upload your test case. When the upload is finished, the dialog box disappears.

View the recorded test case

The recorded test case is now available to be viewed and edited. Open the browser and login to the Jamo Automator tool. The first tab of the tool lists all automated test cases. If the test case Is not displayed, press on the ‘Refresh’ button situated in the upper right corner of the form. In the sample, one test case is listed, i.e. the test case that is just recorded on Android. The name of the case is the name that was given on the device. In the example the name is ‘searchRecipe’.

step3 image 4

Click on the name of the test case. You get the detail form of the test case. The upper part of the form lists the descriptive information of the test case, the lower part lists the specifications of a test case. When recording the first time, you have just one specification. Click on the name of the specification.

step3 image 5

The detail form for the test specification opens. See following sections for an in depth explanation of a test specification. A specification is an implementation of a test case that can be applied for one or more releases of the app. If a new release of the app changes the user interaction for the test case, then a new specification will be created covering the new implementation to deal with the changes.

The detail form of the test specification contains the upper part of the descriptive information. The lower part contains the different views of the specification. A test specification can have been executed on multiple devices. For each model, the tool will save a view. Since this is a fresh recorded test specification, only one view is available, the view on the model on which the new test specification is recorded.

step3 image 6

Select the name of the OS in the left most column of the views. The detail window of the view opens.

step 3 image 7

A view of a test case contains the screenshots for each action that you performed on your app. In the example, we searched for pasta recipes, selected one of them, looked into the ingredients and returned to the home screen.

The left tree contains an overview of the actions. However the mouse across an image in order to get the action and its arguments.