Follow these steps:
The Mobile Testing Step tab opens and shows a screenshot of the test application. The Actions section at the top of the tab shows the individual actions that are performed in the test step.
Inserts a Back command to return to the previous screen in the application. Android only.
Performs a Get on the selected element. The name of the selected element appears next to the Get element option.
Performs a Tap action on the selected element. The name of the selected element appears next to the Tap element option.
Brings up the keyboard and simulates pressing the specified keys to set the value of the text element.
Note: In some instances, the application does not display the typed values. For example, a password field might not display the entered values.
Sets the value for the selected element. The name of the selected element appears next to the Set value option.
Note: You can also use this action to set the value for a slider. For example, setting a value of 0.8 moves the slider 80% to the right. Use increments of 0.1 when setting the value for a slider. Setting a value of 0.25 is unrecognized and does not move the slider.
Performs a long tap on the screen, as opposed to a specific element.
Performs a long tap on the selected element. The name of the selected element appears next to the Long Tap element option.
Inserts a pause in the test. You can express the wait like ThinkTime at the step level. For example, 1s-10s inserts a random pause between 1 and 10 seconds. 100z inserts a pause of 100 milliseconds.
Lets you insert a comment for a specific action. The comment performs no action, it is for documentation only.
Lets you insert an arbitrary beanshell script. Typically, this script does not interact with the device or simulator. This action provides the means of inserting a custom assertion.
Changes the orientation of the device.
Performs a shake gesture on the device.
Performs the action of pressing the home button. This action forces the application to the background for 10 seconds and then brings it back. This action is useful for testing because it typically forces the application to release memory and stop any CPU-intensive work. iOS only.
For more information, see Add an Assertion to a Mobile Test Step.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|