MotionThese are the actions that are used to actually operate a smartphone.
VariablesThese are features to store certain values during a test, or to randomly generate values (numbers, text). The values stored here can be used in other steps.
ControlThese are features that you can use when a scenario requires a branch point or when you need to repeat the same steps.
AssertionThese are features that you use to check for elements or strings appearance in a specific location on the screen. If the assertion action used fails to meet the specified condition, the scenario stops with an error message in red.It is mainly used to verify that the step has progressed well after a particular step is performed (for example, to verify the welcome message after log in).
EventsThese are the various control actions that can be performed on the device, not in Motion. For example, you can turn the portrait screen into a landscape screen, launch or shut down the app, and so on.
AdvancedAdvanced features are included to create an advanced scenario.
It’s a list of actions that are used to actually operate a smartphone.
Action to a screen element. This is the most commonly used action when creating a step, and it is also set to the default value of the action when creating a new step.
Action to touch a screen element as many times.
NTimes Touch Attributes
Action to double touch the screen element.
Double Touch Attributes
(Double Touch Action attributes Example)
Action to touch and hold the screen element.
Long Touch Attributes
(Long Touch Action Attributes Example)
Action to swipe left and right against a swipeable UIObject.
Action to scroll up and down to a screen element. When scrolling through the entire screen, you can use Full Screen Strategy in the UIObject Selector panel to register the screen element in the step.Caution) On Android devices, if there is a touch element in the bottom area or the Navigation bar is set to Swipe gesture, when using the Full Screen Strategy for screen analysis and Scroll action, even though setting the area to 95% or more may result in the Scroll action being performed normally, there may not be any actual change on the screen.
For drag action, you need two target screen elements: dragging is performed from the first screen element to the second screen element.This action is mainly used on screens that set the date or time.
Perform the Zoom in, Zoom out action.
Pinch In / Pinch Out Attributes
Action to enter a specific value from your keyboard. With the keyboard active on the app screen, set the full screen to UIObject and enter the value you want to enter in the Value field in the Attributes panel.
Enter the input value set in Attributes on the security keyboard displayed on the screen.Caution) Full Screen Strategy should be used with the security keyboard turned on.
Secure Keyboard Attributes
These are features to store certain values during a test, or to randomly generate values. The values stored here can be used in other steps.Caution) The key value is not case sensitive.
Action to store specific values.For example, if you need to create a scenario where you need to enter your login ID frequently, you can set the value in advance at the beginning and retrieve it from where you need it.
Store Value Attributes
Action to read and store strings at specific locations on the screen. You can use the key value when you use the value stored here in another step.Please refer to the following example.Example3.
Store Content Attributes
Action to generate random number.
Random Number Attributes
Action to generate random text.Characters used for random generation are lowercase letters (a-z), upper case letters (A-Z), and numbers 0-9.
Random Text Attributes
Action to export variable from shared scenario to the scope of the parent scenario.In order to use the saved value of any variable of ‘Store Value’, ‘Store Content’, ‘Random Number’, and ‘Random Text’ from shared scenario, the variable must be accompanied with Export Variable.
Export Variable Attributes
These features that you can use when a scenario requires a branch point or when you need to repeat the same steps.
Action to use to determine if the set UIObject exists on the screen and run the child step.
If UIObject Attributes
Action to branch conditionally on the comparison of the content of the target element.Please note there is difference between ‘If UIObject’ and ‘If Content’. The difference is that If UIObject uses the screen element itself as a comparison, while If Content uses the Text information contained in it as a comparison rather than the screen element itself.
If Content Attributes
Action to use when using a value stored through a Store Value/Content or Random Number/Text action as a comparison destination. Therefore, there is no need to set a separate UIObject.For more information, please refer to the example below.Example5.
If Value Attributes
Action to use to detect a status of visual changes in the screen within a time interval.By using ‘If Changed’, you can detect visual changes in the content at a specific location on the screen. This is very neat action to detect toast pop-up or playing videos. You can detect this visual abnormality and tie a specific execution or action on this condition. For example, if a movie is playing, you can create a scenario that stops playing the movie using ‘If Changed’.Please refer to the example below.Example6.
If Changed Attributes
Action to repeat child steps depending on whether a particular screen element exists on the screen.The most common use case is when you create a scenario where you need to repeat scrolling until you get the content you want from a listed UI.Please refer to the example below.Example2.
Loop UIObject Attributes
Action to use when you need to repeat the same step in N times.This action repeats the child steps a set number of times.
Loop Ntimes Attributes
Action for conditional loop on the basis of the text value for the screen element. Loop Content reads character value at specific locations on the screen to determine if it needs to repeat.Please check the example below for detailed instructions.Example7.
Loop Content Attributes
Run the child step by comparing the value you set with the value you saved in Store Value/Content or Random Number/Text. You do not need to specify a separate screen element because it uses a preset value.Use this action to create a scenario where you can read and save the remaining points on the previous screen and repeat the steps of adding points until the remaining points reach a certain number.
Loop Value Attributes
Action to wait for a specific target screen element to be appear. Some screen may take a longer time to load. In this case, instead of adjusting the default loading time to a bigger value, you can specify a tailored waiting time pertaining to the specific page with ‘Loop Wait for’. By doing this, your overall test run time can be greatly reduced.
(Example of avoiding whole loading of Google Map by limiting the waiting time for ‘Search Here’ string. This may save test time under slow network or with the low spec devices)
Loop Wait For Attributes
These are features that you use to check for elements or strings in a specific location on the screen. If this step action for assertion failed, the scenario stops with an error message in red.Assertion is the most important and the terminal component of the software testing. It is mainly used to check whether actual execution result is concurred you’re your initial expectation. (for example, to verify the welcome message after log in).
Action to check whether the specified screen element exists on the screen.With this action, you can verify whether the execution of previous step leads to your expectation “visually”. Please refer to the example below for instructions on how to use it.Example9.
Assert UIObject Attributes
(Assert UIObject Attributes Example)
Action that assert the string content of a specified screen element with the value entered by the author.Unlike the Assert UIObject, where the presence of the screen element itself is compared, the text within the screen element is compared instead.
Assert Content Attributes
Action to assert the runtime value with Store Value/Content or Random Number/Text.Because it is an action that checks the value you have set in advance, this action does not require a separate UIObject, unlike Assert Content and Assert UIObject.
Assert Value Attributes
Assert Changed is an action to assert a drastic change after some step execution.This can be used to check whether the content of a particular screen element or location changes after performing an action.Used primarily to create UI or toggle button change detection scenarios that automatically appear or disappear.Please refer to the example below for instructions on how to use it.Example8.
Assert Changed Attributes
(Assert Changed Attributes Example)
Checks whether the specified screen element exists on the screen, similar to the Assert UIObject. However, the difference is that there is the option to choose how long to wait for the screen element to appear.This can be useful mainly for irregular screen loading times.
Assert Wait For Attributes
Action to check if toast pop-ups appear well after a particular action.If an Assert Message detects a change in the screen for a time period set by limit, it reads the characters in the changed part and compares them with the value entered.
Assert Message Attributes
These are the various control actions that can be performed on the device, not in Motion. For example, you can turn the portrait screen into a landscape screen, launch or shut down the app, and so on.
Allows you to change the screen orientation of the device (rotate 270 degrees clockwise)
Wait for the set amount of time to run the next step.
Launch the app.
If you enter both values, the value to be used depends on the type of device on which the test runs.
Step1. Go to play.google.com and search for the app.Step2. The package name on the address bar part the top. ?id=Package Name format.
Step1. Go to apple.com/kr/app-store and search for the app.Step2. Check the unique number in the top address bar. /id unique number format.Step3. Enter the address in the browser in the format below.https://itunes.apple.com/lookup?id=unique numberStep4. Open the downloaded file in txt format to see the Bundle ID value.
Shut down the running app.
Display the app running in the background on the device screen.
Bring up home screen of the device. (Same behavior as pressing the Home button)
Change the device to a locked state
Unlock the device.
Turn off sleep mode when the device is in sleep state.
Action to enter Android specific keycodes.Caution) The Keycode action is an Android-only action. It doesn’t work on the iPhone and just goes straight to the next step.
Advanced features are included to create an advanced scenario. Currently, there are only shared Scenario features, but a future version will provide new features.
Action to include a shared scenario.Learn how to create and use shared scenarios through examples.Example10.
Shared Scenario Attributes