Skip to main content

Command list

  • Updated

Fixed commands

Command name

Content

Launch app

Launch the app to be tested.

  • App launch options
  • (with device reset) This is equivalent to restoring a device to its factory default state. This cannot be used for local PC real devices.
  • (by process restart and cleaning app info)
    • In the case of Android, it is equivalent to first clearing the app data from the Settings app, then closing the app and starting it up again.
    • In the case of iOS, first closing the app, and then the app information is cleared, and after that starting up the app again. However, in the case of BrowserStack or SauceLabs, the app information is cleared by resetting the device to its factory default state, and in the case of a real iOS device on a local PC or in the Remote TestKit environment, app information is cleared by reinstalling the app, so some app information may remain on the device.
  • (by process restart) Equivalent to closing down the app once and relaunching it.
  • (by first-time-only process restart (not recommended))This is equivalent to not doing anything if the app is already launched, but launching it if it is not. The test will start from the screen state at which the previous test ended, and the dependency between tests will become stronger. Therefore, its use is deprecated.

Open browser

Launch the browser to be used in the test.

  • Browser launch options
  • (by process restart) Equivalent to closing down the browser and relaunching it.
  • (by first-time-only process restart with clearing cookies)  This is equivalent to not doing anything if the browser is already launched, but launching it if it is not. Delete cookies for the page domain currently being displayed.
  • (by first-time-only process restart) This is equivalent to not doing anything if the browser is already launched, but launching it if it is not.

 

UI operation

Command name

Content

Tap

(Mobile app testing only) Tap the specified element.

  • UI elements

Double tap

(Mobile app testing only) Tap the specified element twice quickly.

  • UI elements

Flick

(Mobile app testing and mobile emulation of browser testing only) Operate the specified element shortly with your finger (the same operation as when you flick text).

  • UI elements
  • Direction of movement: Flick from the center of the screen toward this direction. Receives any of the character strings “Up”, “Down”, “Left” or “Right”.
  • Movement quantity: If the “Movement direction” is “Up” or “Down”, specify the ratio in relation to the screen height in a form such as “10%”. In case the “Movement direction” is “Left” or “Right”, specify the ratio in relation to the screen width.
  • Pause duration before motion: (Optional) You can set the pause before flick movement in milliseconds. Default value: 0

Drag

(Browser testing only) Drag the specified element.

  • UI elements
  • Direction of movement: Drag from the center of the screen toward this direction. Receives any of the character strings “Up”, “Down”, “Left” or “Right”.
  • Movement quantity: If the “Movement direction” is “Up” or “Down”, specify the ratio in relation to the screen height in a form such as “10%”. In case the “Movement direction” is “Left” or “Right”, specify the ratio in relation to the screen width.

Drag & drop

(Mobile app testing only) Drag the specified element and drop it on another element.

  • Source UI element: This is the dragged element.
  • Destination UI element: This is element it is dropped on.

Coordinate specification

  • Specify the X, and Y coordinates as a percentage, to specify the drag start position or the drop position more flexibly. Usage such as “Drop to the area next to a certain element” is also possible.
    • When (X, Y) = (50, 50), start dragging or drop to the center of the element
    • When (X, Y) = (95, 50), start dragging or drop to the right edge of the element (within the element range)
    • When (X, Y) = (120, 50), start dragging or drop to the position at which the width of the element exceeds 20% from the right edge of the element.
    • When (X, Y) = (-20, 50), start dragging or drop to the position at which the width of the element exceeds 20% from the left edge of the element.
  • Specifying a position beyond the range of the screen may result in an error

Long press & drag

(Mobile app testing only) Long press the specified element and drag it to another element.

  • Source UI element: This is the element long tapped.
  • Destination UI element: This is the destination element.

Pinch out

(Mobile app testing only) Spread the specified element in the vertical direction using two fingers. This is mainly used to enlarge images.

  • UI elements
  • Movement quantity: This is the ratio related to the height of the screen, and is specified in a form such as “10%”. Note that this quantity is equivalent to the distance traveled by the fingers and is different from the ratio at which the element is expanded.

Pinch in

(Mobile app testing only) Move the designated element with two fingers as if you were pinching it to shrink the screen.

  • UI elements
  • Movement quantity: This is the ratio related to the height of the screen, and is specified in a form such as “10%”. Note that this quantity is equivalent to the distance traveled by the fingers and is different from the ratio at which the element is shrunk.

Swipe

(Mobile app testing only) This is the operation of moving the entire screen with a sweeping motion of the finger (this is the same operation as scrolling between or switching screens).

  • Start X-coordinate: The X-coordinate (as measured from the upper left corner of the screen to the right) at which the swipe will begin. This is the ratio to the width of the screen, and is specified in a form such as “10%”.
  • Start Y-coordinate: The Y-coordinate (as measured from the lower left corner of the screen downwards) at which the swipe will begin. This is the ratio to the height of the screen, and is specified in a form such as “10%”.
  • Movement direction: Stipulates the angle of the movement direction from 0 to 360 degrees. In case of up, this is “0”, right is “90”, down is “180”, and left is “270”.
  • Movement quantity: In case the movement direction is from 0 to 90 degrees, "100%" indicates the length from the bottom left of the screen to the point where the line drawn at that angle intersects the top or right edge of the screen. The same concept is used to calculate lengths for other movement directions.
  • Pressure: This specifies the pressing strength of your fingers when swiping (for iOS only, this function is compatible with 3D touch). The relationship between the pressure value and the app behavior depends on the app. Generally, however, 1.0 is the maximum value.
  • Pause duration before motion: (Optional) You can set the pause before swipe movement in milliseconds. Default value: 0
  • Velocity: (Optional) By selecting a non-default value, the amount of distance in a single swipe increases. Default value: Slow and constant

Draw a figure by freehand

(Mobile app testing only) Draw a freehand shape on the entire screen. The order is also recorded and drawn in that order.

  • Figure name: The displayed title of the figure
  • Pressure: This specifies the pressing strength of your fingers when swiping (for iOS only, this function is compatible with 3D touch). The relationship between the pressure value and the app behavior depends on the app. Generally, however, 1.0 is the maximum value.

Continue swipe

(Mobile app testing only) Continue to swipe until the specified element is displayed on the screen. This can be utilized if you want to display an element outside the scroll range. Reference:Method of operating screens where scrolling is required

  • UI elements
  • Swipe target: Specifies what part of the screen to swipe. If you select “Entire Screen,” and choose “UE element” from the center of the screen, you will operate from the center of the selected element.
  • Movement direction: Repeat the swipe from the center of the swipe target in this direction. Receives any of “Up,” “Down,” “Left” or “Right”. If you swipe the screen up, the screen is scrolled to the bottom, so be careful not to make a mistake with this.
  • Maximum number of times: Maximum number of times to swipe.
  • Velocity: (Optional) By selecting a non-default value, the amount of distance in a single swipe increases. Default value: Slow and constant

Long tap

(Mobile app testing only) Long tap the specified element.

  • UI elements
  • Press duration: (Optional) You can configure the duration, in milliseconds, for which the element remains pressed. Default value: 600

Tap specified position

(Mobile app testing only) Tap the specified element in specific position.

  • UI elements
  • Position: Specifies what position within the element to tap. “Center”, “Left edge”, “Top edge”, “Bottom edge”, “Top left corner”, “Top bottom corner”, “Top right corner”, “Bottom right corner”, and “Coordinates” can all be specified.

Coordinate specification

Specify the X, and Y coordinates as a percentage, to specify the tap position more flexibly. Usage such as “Tap the area next to a certain element” is also possible.

  • When (X, Y) = (0, 0), tap the top-left corner of the element
  • When (X, Y) = (50, 50), tap the center of the element
  • When (X, Y) = (100, 100), tap the bottom-right corner of the element
  •  When (X, Y) = (95, 50), tap the right edge of the element (within the element range)
  • When (X, Y) = (120, 50), tap the position at which the width of the element exceeds 20% from the right edge of the element.
  • When (X, Y) = (-20, 50), tap the position at which the width of the element exceeds 20% from the left edge of the element.
  • Specifying a position beyond the range of the screen may result in an error

Multi touch action

at the screen center

(Mobile app testing only) Screen operation performed with multiple fingers.

  • Number of fingers: Specifies number of fingers with which to perform the operation. Currently, only 2 or 3 fingers is supported.
  • Operation type: Select the content of the operation from “Tap”, “Double tap” and “Long tap”.

Tap system button

(Mobile app testing only) This is the operation of pressing system buttons, such as “Home” or “Back”. As buttons such as Android’s “Home” or “Back”, etc. may not currently be easily pressable in MagicPod even if they are visible on the screen capture, please use this command.

  • System button type: Type of button pressed. Currently, “Home” (iOS and Android), “Back”, “Menu”, “App list” (Android only) are supported.
  • With long press: (Optional) Long press the button instead of tap. Default value: No

Check (WebView)

(Mobile app testing only) State in which the specified element (checkbox) is checked. This can only be used in relation to HTML element on WebView.

  • UI elements

Uncheck (WebView)

(Mobile app testing only) This is the state in which the specified element (check box) is left unchecked. This can only be used in relation to HTML element on WebView.

  • UI elements

Click

(Browser testing only) Clicks the specified element.

  • UI elements

Double click

(Browser test only) Double-click the specified element.

  • UI elements

Right click

(Browser testing only) Right-click the specified element.

  • UI elements

Click with special key

(Browser testing only) Click the specified element with a special key held down.

  • UI elements
  • Key type: Type of pressed key. In case of “Shift”, “Alt (in case of Mac, Option)”, “Control”, “Meta (in case of Mac, Command” are supported.

Click and

download file

(Browser testing only) Click the specified element, and then, for IE only, perform file save as... operation. For details, refer here.

  • UI elements

Click and

upload file

(Browser testing only) Click the specified element (element for selecting file), and upload a file saved to MagicPod in advance. For details, refer here.

  • UI elements
  • Uploaded file (multiple files can be selected)

Check

(Browser testing only) Set specified element (checkbox) to checked state.

  • UI elements

Uncheck

(Browser testing only) Set the specified element (checkbox) to unchecked state.

  • UI elements

Click specified position 

(Browser testing only) Click a specific position on the specified element.

  • UI elements
  • Position: Specify what position within the element to click. “Center”, “Left edge”, “Top edge”, “Bottom edge”, “Top left corner”, “Top bottom corner”, “Top right corner”, “Bottom right corner”, and “Coordinates” can all be specified.

Coordinate specification

Specify the X, and Y coordinates as a percentage, to specify the click position more flexibly. Usage such as “Click the area next to a certain element” is also possible.

  • When (X, Y) = (0, 0), click the top-left corner of the element
  • When (X, Y) = (50, 50), click the center of the element
  • When (X, Y) = (100, 100), click the bottom-right corner of the element
  • When (X, Y) = (95, 50), click the right edge of the element (within the element range)
  • When (X, Y) = (120, 50), click the position at which the width of the element exceeds 20% from the right edge of the element.
  • When (X, Y) = (-20, 50), click the position at which the width of the element exceeds 20% from the left edge of the element.
  • Specifying a position beyond the range of the screen may result in an error

Continue scroll

(Browser testing only)

  • Automatically
    • Scroll the whole page until the specified element is displayed. Automatically detect and scroll an element that needs to be scrolled to display the specified element. "Automatically" mode sometimes doesn’t work well depending on the structure of web pages or target UI elements. In such case, please specify the scrolled target by selecting "Whole screen" or "UI element" mode.
  • Whole screen
    • Scroll the whole page until the specified element is displayed. "Moving direction" and "Maximum number of times" are usually automatically calculated, so they are ignored even if specified. When using the AI locator or when the element does not exist on the screen at the start of scrolling, the automatic calculation cannot be performed, so scrolling is repeated until the element is found to the specified "moving direction" for the "maximum number of times".
      • UI elements
      • Movement Direction: Scroll direction. Any of "Downward", "Upward", "Leftward", and "Rightward".
      • Maximum number of times: Maximum number of times to scroll.
  • UI element
    • Scroll through the scrollable elements (must be specified), including that element, until the specified element is displayed. Use when you want to scroll only part of the screen, such as a side menu.
      • UI element 1: This is the scrolled element. In many cases, you specify the whole area you want to scroll, which has scrollbars.
      • UI element 2: This is the element inside UI element 1 to which it scrolls.

Hover

(Browser testing only) Hover the specified element.

  • UI elements
  • The plan is for “Pinch out" and "Pinch in" to support pinches in directions other than the vertical direction in the future.
  • Direct numerical specification of the “%” argument will be supported in the future.

 

UI input

Command name

Content

Input

Sets the text for the specified element. If the specified element is an element that cannot accept text entry, this command will fail. If you want to forcibly send text to an element that does not accept text entry, you can use the “Input keyboard key” command on the mobile app.

  • UI elements
  • Character string: Set text
  • Retry count: (Optional) Retry input until the specified text is correctly set. Default value: 0
  • Input method: (Optional) By selecting “Append to the current text”, you can append text to the existing content. Default value: “Overwrite the current text”

Input to picker

Set value to picker. In the case of Android, the value is set by entering the value key, whereas in iOS it is set by swiping the picker a little at a time.

Character string: Set value

  • UI elements
  • Swipe direction: In the case of iOS, this is the direction in which you swipe. “Auto” is effectively the same as determining the direction for numeric items based on the size of the number, and determining non-numeric items as “Up then down”. In the case of “Up then down” and “Down then up”, swiping to the edge switches the direction of the swipe. In the case of “Up” and “Down”, swipe in one direction to the edge. If you swipe the picker up, the value one below the picker value shall be selected, so be careful not to make a mistake in this regard.
  • Maximum number of times: In the case of iOS picker, this is the maximum number of times to swipe.

Input keyboard key

This is an operation to press special keys on the keyboard, such as “Enter” or “Delete”, etc.

  • Key type: Type of pressed key. In the case of the mobile app, “Enter”, “Search”, “Send”, “Complete”, “Run”, “Next”, “Delete”, “0” through “9”, and “Text” are supported (in case of the “Search”, “Send”, “Complete”, “Run” “Next” buttons, in many cases you can also press the “Enter” button. ). In the case of “Text”, the specified text is sent to the element currently in focus.
  • Text: This can only be specified when “Key type” is “Text”.

Toggle switch

Switches the specified element (switch) state (ON/OFF).

  • UI elements
  • State: Set state (ON/OFF)

Select pull-down menu(WebView)

Select the specified character string from the pulldown menu. This can only be used in relation to HTML element on WebView. It can only be used with a HTML standard select element. (Detail)

  • UI elements
  • Character string: This is the selected character string.
  • Check the value after selected: (Optional) After selected, assert that the displayed value is equal to the specified value. (Detail) Default value: Yes

Select pull-down menu

(Browser testing only) Select the specified character string from the pulldown menu. It can only be used with a HTML standard select element. (Detail)

  • UI elements
  • Character string: This is the selected character string.
  • Check the value after selected: (Optional) After selected, assert that the displayed value is equal to the specified value. (Detail) Default value: Yes

 

System

Command name

Content

Launch test target app

Launches the process of the app to test. If the app is already launched, the process is stopped once and relaunched. If “Clear app information” is specified when launching the test the first time, the app information is cleared again at this point.

Terminate app

Closes the current app process. The closed app can be relaunched with the “Launch tested app” command.

Inactivate app

This puts the process of the app to test in the background (the process does not end). Apps in the background can be put in the foreground with the “Put app in foreground” command.

Activate app

This puts the process of the app to test in the foreground. If the app to test is closed, relaunch the app to test.

Launch other app (iOS)

Launching apps other than apps to test. When specifying other than the “Bundle ID”, the app is also installed (if it is already installed, it will be reinstalled).

  • Target app: You can also specify “App/IPA file URL”, “App/IPA file (cloud upload)”, “App/IPA file path”, or “Bundle ID”.

Launch other app (Android)

Launching apps other than apps to test. If you specify other than “App package”, the app is also installed (if it is already installed, it will be reinstalled ).

  • Target app: You can also specify “APK/AAB file URL”, “APK/AAB file (cloud upload)”, “APK file path”, or “App package”.

Hide keyboard

If the keyboard is displayed, hide the keyboard. This can be used in cases where other elements are hidden by the keyboard and the keyboard must be hidden to proceed. In the case of iOS, you can hide the keyboard by tapping keyboard buttons, such as “Complete”, “Search”, or “Go”. If these buttons are not on the keyboard, the hide operation may not complete successfully. (Note that buttons such as “Complete” that are outside the keyboard will not be tapped).

Rotate screen

Rotates the orientation of the app screen.

  • Orientation: Orientation of the screen. Specify “vertical-facing” or “horizontal-facing”.

Set clipboard value

Set the specified text on the clipboard of the device.

  • Text: This is the text set on the clipboard.

Take screenshot

Acquire a screen capture of the current screen. The acquired screen captures can be viewed on the test results screen.

  • Screen capture name: This will be the file name when the test result screen capture is downloaded by the command “Download results of command to acquire screen capture” command.”

Shake (Simulator/

Emulator)

Shake the device in the horizontal direction. This command can only be used for the iOS simulator and Android emulator.

Web API call

Call Web API (REST API). Reference: Web API call

Set geolocation

Set arbitrary geolocation to the browser or mobile device. Reference: Setting Position Information

  • Name
  • Geolocation: A point designated by latitude and longitude

Push image to device

Place the image file on the device to be tested. iOS real devices are not supported.

  • Image file: Image file to be placed. You can register a file up to a maximum of 5 MB.

Back

(Browser testing only) Perform same operation as when browser Back button is pressed down.

Forward

(Browser testing only) Perform same operation as when browser Forward button is pressed down.

Reload

(Browser test only) Perform same operation as when browser Reload button is pressed down.

Open new tab/window

(Browser testing only) Open new window/tab. Note that you cannot automatically move operation to a new window/tab simply by opening a window/tab.

Select new tab/window

(Browser testing only) When multiple windows/tabs are open, select the last opened window. Note that the operation cannot be automatically transferred to the new window unless this command is run.

Select previous tab/window

(Browser testing only) When closing the operated window/tab, select the window operated on before the most recently operated window. Note that you cannot automatically move operation to an old window simply by closing a window.

Close tab/window

(Browser testing only) Close the currently operated window/tab with the X button. This operation is not required if the window was originally designed to be closed by some operation on the page (such as by clicking a button).

Close alert

(Browser testing only) Close the JavaScript alert dialog box.

  • OK/Cancel: If you can choose between OK/Cancel for the alert, choose one of these and close.

Set cookie

(Browser testing only) Set a browser cookie for the currently displayed page domain.

  • Name: The name of a cookie
  • Value: The value of a cookie

Clear cookies

(Browser testing only) Delete the browser cookies for the currently displayed page domain.

Set value to

local storage

Set the Local Storage value.

  • Key: Local Storage key
  • Value: Local Storage value

Clear local storage

Delete all Local Storage keys/values.

Set value to

session storage

Set value in session storage.

  • Key: Session Storage key
  • Value: Session Storage value

Clear session storage

Delete all session Storage keys and values.

Set UI element's attribute

(Browser testing only) Set values stipulated in the UI variable attributes.

  • UI elements
  • Character string: Attribute name
  • Character string: Set attribute value

Arithmetic operation

Save the specified calculation results as a variable. The resulting values are not comma-separated values, but are rounded to the nearest whole number of decimal places.

  • Variable name: Variable name. This can be in Japanese, too.
  • Left side
  • Operators: “+”, “-”, “×”, or “÷”
  • Right side

Date calculation

Save the specified date/time as a variable. It is possible to save it in various formats. You can also specify the date format of your choice. Reference:How to write date formats

  • Variable name: Variable name. This can be in Japanese, too.
  • Date/time: Saved date/time value

Comment

You can write comments. Nothing will happen when running a test.

  • Comment character string
  • Character string: Comment character string

Blank line

You can put lines with nothing on them into scripts. Nothing will happen when running a test.

Output to log

You can output any string (including variable values) to the log. Output limit is 10,000 characters.

Fail

You can make the test fail with the message.

  • Character string: Message character string

 

Assertion

  • Failure behavior: "Stop on failure" or "Mark as failure and continue"
    • You can select for all assertion commands except the "Assert no visual diff" command.

Command name

Content

Assert UI element equals

Check that the UI element text matches the specified character string.

  • UI elements
  • Character string: Expected text value

Assert UI element does not equal

Check whether the UI element text does not match the specified character string.

  • UI elements
  • Character string: Compared text value

Assert UI element contains

Check whether the UI element text includes the specified character string.

  • UI elements
  • Character string: Expected text value

Assert UI element does not contain

Check that the UI element text does not confirm the specified character string.

  • UI elements
  • Character string: Compared text value

Assert UI element satisfies numerical comparison

Check that the UI element text satisfies the specified numerical comparison conditions.

  • UI elements
  • Character string: Compared value
  • Comparison conditions Select from “equal”, “not equal”, “bigger”, “same or bigger”, “smaller”, or “same or smaller”.

Assert UI element exists

Check that the UI element exists on the screen.

  • UI elements

Assert UI element does not exist

Check that the UI element does not exist on the screen.

  • UI elements

Assert UI element is enabled

Check that the UI element exists on the screen and is in enabled (not grayed-out) state.

UI elements are considered disabled if either of the following conditions are met.

  • Condition 1: The element is a button, input, select, textarea, or form-associated custom element, and the disabled attribute is specified on this element. (Note: The element is considered disabled even if the value of the disabled attribute is false)
  • Condition 2: The element is a descendant of a fieldset element whose disabled attribute is specified, and is not a descendant of that fieldset element's first legend element child, if any.

If this command does not work, use Assert UI element's attribute satisfies condition command.

  • UI elements

Assert UI element is disabled

Check that the UI element exists on the screen in disabled (grayed out) state. Please check the above for conditions that are judged to be disabled.

  • UI elements

Assert UI element is selected

Check that the checkboxes, switches, or radio buttons are in selected state.

  • UI elements

Assert UI element is not selected

Check that the checkboxes, switches, or radio buttons are not selected.

  • UI elements

Assert UI element is visible

Check that the UI elements exist on the screen and that they are displayed. UI elements are considered visible if both of the following conditions are met:

  • Condition 1: The UI element exists on the screen.
  • Condition 2: The attribute of the UI element 'visible' or 'displayed' is 'true'.

In the case of iOS, this command is unstable, and so use “Check whether it exists” instead.

  • UI elements

Assert UI element is invisible

Check that UI elements are hidden or do not exist on the screen. In the case of iOS, this command is unstable, and so use “Check whether it exists” instead. Please check the above for conditions that are judged to be invisible.

  • UI elements

Assert UI element's attribute satisfies condition

Check that the attributes of the UI element and their values satisfy the specified conditions.

  • UI elements
  • Character string: Attribute name
  • Character string: Compared attribute value
  • Conditions: Select from whether conditions “Match”, “Do not match”, “Include”, “Do not include”, “Exists”, and “Does not exist”.

Assert there is no visual diff

Check that the content of the current screen matches the expected value image. Check here for details.

  • Visual diff check name

Assert title equals

(Browser testing only) Check whether the browser title matches the specified character string.

  • Character string: Expected title value

Assert title does not equal

(Browser testing only) Check whether the browser title does not match the specified character string.

  • Character string: Compared title value

Assert title contains

(Browser testing only) Check whether the browser title includes the specified character string.

  • Character string: Expected title value

Assert title does not contain

(Browser testing only) Check whether the browser title does not include the specified character string.

  • Character string: Compared title value

Assert URL equals

(Browser testing only) Check whether the current page URL matches the specified character string.

  • Character string: Expected URL value

Assert URL does not equal

(Browser testing only) Check whether the current page URL does not match the specified character string.

  • Character string: Compared URL value

Assert URL contains

(Browser testing only) Check whether the current page URL includes the specified character string.

  • Character string: Expected URL value

Assert URL does not contain

(Browser testing only) Check whether the current page URL does not include the specified character string.

  • Character string: Compared URL value

Assert alert message

equals

(Browser testing only) Check whether the current JavaScript alert dialog box is displayed and the message content matches the specified character string.

  • Character string: Expected message value

Assert alert message contains

(Browser testing only) Check whether the current JavaScript alert dialog box is displayed and the message content contains the specified character string.

  • Character string: Expected message value

Assert alert tab/window is  closed

(Browser testing only) Check whether the window that was operated immediately before the command is already closed.

Assert download is completed

(Browser testing only) Check whether a file with the specified name exists in the Downloads folder.

  • File name: Specifies only the file name, rather than the path to the folder. Regular expressions can also be used. (Example: "MagicPodDesktop-0.28.0.zip", "MagicPodDesktop-.*.zip", etc.)

Assert variable equals

Check that the variable name matches the specified character string.

  • Variable
  • Character string: Expected value of the variable

Assert variable does not equal

Check that the variable name does not match the specified character string.

  • Variable
  • Character string: Compared variable value

Assert variable contains

Check that the variable value includes the specified character string.

  • Variable
  • Character string: Expected value of the variable

Assert variable does not contain

Check that the variable does not include the specified character string.

  • Variable
  • Character string: Compared variable value

Assert variable satisfies numerical comparison

Check that the variable value satisfies the specified numerical comparison condition.

  • Variable
  • Character string: Compared value
  • Comparison conditions Select from “equal”, “not equal”, “bigger”, “same or bigger”, “smaller”, or “same or smaller”.

Assert UI element's image matches

Check that the difference between the stored image of a UI element, which can be stored by Store image of UI element command, and the image of a selected UI element falls within the predetermined threshold.

  • UI elements
  • Variable
  • Threshold

Assert UI element's image does not match

Check that the difference between the stored image of a UI element, which can be stored by Store image of UI element command, and the image of a selected UI element is out of the predetermined threshold.

  • UI elements
  • Variable
  • Threshold

 

Wait

Command name

Content

Wait until UI element equals

Wait for the UI element text to match the specified character string.

  • UI elements
  • Character string: Expected text value
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element does not equal

Wait for the UI element text not to match the specified character string.

  • UI elements
  • Character string: Compared text value
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element contains

Wait until the UI element text includes the specified character string.

  • UI elements
  • Character string: Expected text value
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element does not contain

Wait until the UI element does not include the specified character string.

  • UI elements
  • Character string: Compared text value
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element satisfies numerical comparison

Wait until the UI element text satisfies the specified numerical comparison results.

  • UI elements
  • Character string: Compared value
  • Comparison conditions Select from “equal”, “not equal”, “bigger”, “same or bigger”, “smaller”, or “same or smaller”.
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element exists

Wait until the UI element appears on the screen.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element does not exist

Wait until the UI element does not exist on the screen.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element is  enabled

Wait until the UI element is enabled (not grayed-out).

UI elements are considered disabled if either of the following conditions are met.

  • Condition 1: The element is a button, input, select, textarea, or form-associated custom element, and the disabled attribute is specified on this element. (Note: The element is considered disabled even if the value of the disabled attribute is false)
  • Condition 2: The element is a descendant of a fieldset element whose disabled attribute is specified, and is not a descendant of that fieldset element's first legend element child, if any.

If this command does not work, use Wait until UI element's attribute satisfies condition command.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element is  disabled

Wait until the UI element is disabled (in grayed-out state). Please check the above for conditions that are judged to be disabled.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element is  selected

Wait until the checkboxes, switches, or radio buttons are selected.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element is not selected

Wait until the checkboxes, switches, or radio buttons are not selected.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element is visible

Wait until the UI element is displayed on the screen. In the case of iOS, this command is unstable, and so use “Wait until it exists” instead.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element is  invisible

Wait until the UI element is hidden on the screen or until it does not exist on the screen. In the case of iOS, this command is unstable, and so use “Wait until it does not exist” instead.

  • UI elements
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until alert message equals

(Browser test only) Wait until the JavaScript alert dialog box is displayed and the content of this message matches the specified character string.

  • Character string: Expected message value
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until alert message contains

(Browser testing only) Wait until the JavaScript alert dialog box is displayed and the content of this message includes the specified character string.

  • Character string: Expected message value
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until UI element's attribute satisfies condition

Waits for the UI element attributes and their values to satisfy the specified conditions.

  • UI elements
  • Character string: Attribute name
  • Character string: Compared attribute value
  • Conditions: Select from whether conditions “Match”, “Do not match”, “Include”, “Do not include”, “Exists”, and “Does not exist”.
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait until screen is rendered

Wait for the entire screen drawing process to complete.

  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

Wait for fixed seconds

Wait only for the specified time. If you use this command within the test, it is easy to cause timing-dependent problems, so you should note this when using.

  • Wait time: Specifies the wait time in seconds. Numbers after the decimal point can also be specified.

Wait until download is  completed

(Browser testing only) Wait until the file with the specified name is downloaded into the Downloads folder.

  • File name: Specifies only the file name, rather than the path to the folder. Regular expressions can also be used. (Example: "MagicPodDesktop-0.28.0.zip", "MagicPodDesktop-.*.zip", etc.)
  • Maximum number of seconds: Number of seconds after which an error occurs if the wait is not exceeded.

 

Variable

Command name

Content

Store value

Saves the element text as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.

Store existence state

Save whether element exists as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference: Utilizing variables

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.

Store enabled state

Saves element enabled state as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.

Store selected state

Saves the selected state of checkboxes and switches as variables. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.

Store visible state

Save element display state as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. In the case of iOS, this command is unstable, and so use “Save existing state” instead. Reference:Utilizing variables

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.

Store attribute

Saves the element attribute value as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.
  • Character string: Attribute name

Store title

Save page title as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.

Store URL

Saves page URL as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.

Store alert message

Save currently displayed JavaScript alert dialog box message as a variable If the alert does not exist, an error will occur. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference :Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.

Store local storage value

Saves the Local Storage specified key value as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.
  • Key: Local Storage key

Store session storage value

Saves the Session Storage specified key value as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.
  • Key: Session Storage key

Store unique value generated based on the current time

Saves a unique number generated based on the current time (seconds) as a variable. It can be used for applications such as registering a new user name with a new ID each time. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.

Store fixed value

Saves fixed value as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.
  • Character string: Saved value. Here, you can also use a different variable value.

Store substring matching regular expression

Saves the first part of the specified text matching the regular expression as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.
  • Text: From the entire text, look for patterns that match the regular expression.
  • Regular expression: Search for character string matching the regular expression.

Store the result of the replacement

Substitutes all parts of the specified text that match a string or regular expression with the specified string and stores the result in a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.
  • Text: Search for a pattern matching the character string or regular expression from this text as a whole.
  • Condition: You can select the condition as “Character string” or “Regular expression”.
  • Character string or regular expression: Specifies the character string or regular expression to search for.
  • Character string: Specifies the character string after substitution.

Store clipboard value

Saves the mobile device clipboard value as a variable. Use when combining with the “Check that the variable value matches” command, and you want to check the clipboard value. Not supported with iOS real devices and Web app tests. Reference:Utilizing variables

  • Variable name: Variable name. This can be in Japanese, too.

Store 2FA passcode

Generates the 6-digits passcode for two-factor authentication and saves this as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

Store text file contents

(Browser testing only) Reads the content of a text file (TXT, CSV file) that is downloaded using the file download command and saves it as a variable. The saved variable value can be referenced in subsequent command arguments in the form ${variable name}. Reference:Utilizing variables

  • Text: The name of downloaded file. Regular expressions can also be used. (Example: "data_file_ver2.txt", "data_file_ver.*\.txt", etc.)
  • Variable name: Variable name. This can be in Japanese, too.

Store image of UI element

Store the image of a selected UI element to a variable. This variable can be used in commands Assert UI element's image matches and Assert UI element's image does not match.

  • UI elements
  • Variable name: Variable name. This can be in Japanese, too.

 

Conditional

Command name

Content

If UI element equals

As long as the UI element text matches the specified character string, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Expected text value

If UI element does not equal

As long as the UI element text does not match the specified character string, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Compared text value

If UI element contains

As long as the UI element text includes the specified character string, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Expected text value

If UI element does not contain

As long as the UI element text does not include the specified character string, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Compared text value

If UI element satisfies numerical comparison

As long as the UI element text matches the specified numeric comparison, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Compared value
  • Comparison conditions Select from “equal”, “not equal”, “bigger”, “same or bigger”, “smaller”, or “same or smaller”.

If UI element exists

As long as the UI element exists on the screen, the processing is run between it and the “End continual branching” command. Reference:Utilizing conditional branching

  • UI elements

If UI element does not exist

As long as the UI element does not exist on the screen, the processing is run between it and the “End continual branching” command. Reference:Utilizing conditional branching

  • UI elements

If UI element is enabled

As long as the UI element is enabled (not grayed out), the processing is run between it and the “End continual branching” command. Reference:Utilizing conditional branching

UI elements are considered disabled if either of the following conditions are met.

  • Condition 1: The element is a button, input, select, textarea, or form-associated custom element, and the disabled attribute is specified on this element. (Note: The element is considered disabled even if the value of the disabled attribute is false)
  • Condition 2: The element is a descendant of a fieldset element whose disabled attribute is specified, and is not a descendant of that fieldset element's first legend element child, if any.

If this command does not work, use If UI element's attribute satisfies condition command.

  • UI elements

If UI element is disabled

As long as the UI element exists, but is disabled (grayed out), the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching  Please check the above for conditions that are judged to be disabled.

  • UI elements

If UI element is selected

Only in cases where the checkboxes, switches, or radio buttons are selected, is the process run between it and the "End Conditional Branch" command. Reference:Utilizing conditional branching

  • UI elements

If UI element is not selected

Only in cases where the checkboxes, switches, or radio buttons are not selected, is the process run between it and the "End Conditional Branch" command. Reference:Utilizing conditional branching

  • UI elements

If UI element is visible

As long as the UI element text is displayed, the processing is run between it and the “End conditional branching” command. In the case of iOS, this command is unstable, and so use “If it exists” instead. Reference:Utilizing conditional branching

  • UI elements

If UI element is invisible

As long as the UI element text is hidden, the processing is run between it and the “End conditional branching” command. In the case of iOS, this command is unstable, and so use “If it does not exist” instead. Reference:Utilizing conditional branching

  • UI elements

If UI element's attribute satisfies condition

As long as the UI element text attribute and its value satisfy the specified condition, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Attribute name
  • Character string: Compared attribute value
  • Conditions: Select from whether conditions “Match”, “Do not match”, “Include”, “Do not include”, “Exists”, and “Does not exist”.

If alert message equals

As long as the JavaScript alert dialog box message matches the specified character string, the processing is run between it and the “End conditional branching” command. If the alert does not exist, an error will occur. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Expected message value

If alert message contains

As long as the JavaScript alert dialog box message is included in the specified character string, the processing is run between it and the “End conditional branching” command. If the alert does not exist, an error will occur. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Expected message value

If variable equals

As long as the variable value matches the specified character string, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • Variable
  • Character string: Expected value of the variable

If variable does not equal

As long as the variable value does not match the specified character string, the processing is run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • Variable
  • Character string: Compared variable value

If variable contains

As long as the variable value is included in the specified character string, the processing will be run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • Variable
  • Character string: Expected value of the variable

If variable does not contain

As long as the variable value does not match the specified character string, the processing will be run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • Variable
  • Character string: Compared variable value

If variable satisfies numerical comparison

As long as the variable value satisfies the specified numerical comparison condition(s), the processing will be run between it and the “End conditional branching” command. Reference:Utilizing conditional branching

  • UI elements
  • Character string: Compared value
  • Comparison conditions Select from “equal”, “not equal”, “bigger”, “same or bigger”, “smaller”, or “same or smaller”.

Otherwise

As long as the conditions of “If...” and “Otherwise, if...” commands are not met, the processing will be run between it and the “End conditional branching” command. Reference: Utilizing conditional branching

End branch

Use the various conditional branching commands as pairs. The processing between the respective conditional branching command and “End conditional branching” command becomes the processing to run when conditions match. Reference:Utilizing conditional branching

 

Unimplemented commands

Command name

Content

Lock

Work-in-progress

Unlock

Work-in-progress

Wait until drawing ends

Waits until element drawing process completes. This command enables waiting for elements for which the drawing process does not end for a while even after being displayed on the screen.

  • UI elements
Was this article helpful?
0 out of 0 found this helpful
If the problem persists, please contact us from here.
Contact
Return to top

Related articles