SeeTestAutomation- Object Commands
Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .
The Object commands include the following:
- SeeTestAutomation - Click
- SeeTestAutomation - Click(Offset)
- SeeTestAutomation - ClickCoordinate
- SeeTestAutomation- ClickIn
- SeeTestAutomation - Drag
- SeeTestAutomation- ElementGetProperty
- SeeTestAutomation - ElementGetTableRowsCount
- SeeTestAutomation- ElementListPick
- SeeTestAutomation- ElementListSelect
- SeeTestAutomation- ElementListVisible
- SeeTestAutomation - ElementScrollToTableRow
- SeeTestAutomation - ElementSendText
- SeeTestAutomation- ElementSetProperty
- SeeTestAutomation - ElementSwipe
- SeeTestAutomation - ElementSwipeWhileNotFound
- SeeTestAutomation - FlickCoordinate
- SeeTestAutomation - FlickElement
- SeeTestAutomation - GetAllValues
- SeeTestAutomation - GetElementCount
- SeeTestAutomation - GetElementCountIn
- SeeTestAutomation - GetTextIn
- SeeTestAutomation- IsElementBlank
- SeeTestAutomation - IsElementFound
- SeeTestAutomation - IsFoundIn
- SeeTestAutomation - LongClick
- SeeTestAutomation- RunNativeAPICall
- SeeTestAutomation - SendWhileNotFound
- SeeTestAutomation - VerifyElementFound
- SeeTestAutomation - VerifyElementNotFound
- SeeTestAutomation - VerifyIn
- SeeTestAutomation- WaitForElement
- SeeTestAutomation - WaitForElementToVanish
- SeeTestAutomation - GetCoordinateColor
- SeeTestAutomation - DragDrop
- SeeTestAutomation- ForceTouch
- SeeTestAutomation - Touch Commands
- SeeTestAutomation - TouchCoordinate Commands
- SeeTestAutomation - Gesture commands
- SeeTestAutomation- setPickerValues
Controlling Element Identification Rules
When running a test step on a Native element, SeeTest requires certain rules to be met in the found element's properties before it starts performing the actual step on it.
One rule is that the element is not "busy". a busy element is an element that is still being drawn by the Operation System of the device or is busy showing some animation.
In case the element is found in such state, SeeTest will wait for it to get idle for a certain time (1 Second by default), and then gives up waiting and performs the step of the busy element.
The following lines can be added to %appdata%\seetest\app.properties file in order to modify this default behavior:
(*) element.idle.timeout=<timeout to wait for busy element in milliseconds> (1500 by default)
(*) assert.element.idle=<true/false> - if element is not found till timeout - should SeeTest use the busy element or assert it is idle (false by default)
Another rule forced on the element's properties, is that it does not have zero size. Elements with zero size (width or height) are often (especially in web applications) deflated elements that the application intends to inflate when they are required.
The following lines can be added to %appdata%\seetest\app.properties file in order to modify this default behavior:
(*) assert.element.dimension=<true/false> - should SeeTest ignore elements with 0 width or height, true by default.