- Introduction
- Manual testing
- Autoit
- Ant
- Agilitest
- Bat
- Bat With Params
- Beanshell
- Cerberus
- Cucumber
- Cucumber v2 (BDD & Gherkin support)
- eTASQ Motion (Ponant)
- Executable
- FitNesse
- Gatling
- Generic Version-Control
- Git, Gitlab, Github
- Gradle
- Java
- Jar
- JMeter
- JMeter SQL
- JMeter Web
- JUnit
- Katalon
- Katalon v2
- Marathon
- Maven
- Mocha
- NeoLoad
- NUnit
- Odin Axe
- Odin Axe Results
- Offline
- Perl
- PHPUnit
- Postman (Newman)
- Protractor
- Python
- PyUnit
- PyTest
- QF-Test
- Quick Test Pro/UFT
- Ranorex
- Rapise
- RobotFramework
- RobotFramework v2
- RobotFramework v3
- RobotFramework v4
- Sahi
- Sahi 3.5
- Sahi 4.0
- Sahi 6.0
- Selenese
- Selenium HTML
- Selenium 3
- Selenium Java
- Selenium .NET
- Selenium Python
- Shell
- Sikuli
- SikuliX
- SilkTest
- SoapUI
- SoapUI Load
- SoapUI Security
- SOATest
- SQL Compare
- SQL Select
- Squish
- SVN (Subversion)
- Tape
- Tcl
- TestComplete
- TestComplete v2
- TestExecute
- TestExecute v2
- TestNG
- TestOptimal
- TestOptimal Simple
- TestPartner
- TestStand
- VisualStudio
- VisualStudio Coded UI
- WAPT
- WebdriverIO
- WebUI
- XCI
- xUnit.net
- Success (skeleton)
- Random (skeleton)
- Proxy
eTASQ Motion (etasq.jar)
The eTASQ Motion launcher allows interfacing with Ponant's eTASQ Motion Robot to execute some sequences of actions (keywords) on physical devices such as smartphones.Configuration
Theetasq.xml
file is a template and must NOT be edited. It's used by the system to build dynamically the form that the user will be able to fill in from the GUI when creating an execution configuration.Parameter | Description |
REST Connection | |
Base URL | This must indicate the base URL of your eTASQ Motion server's REST API. This URL MUST not include an ending slash. Default value is: http://12.34.56.78:8091/v0
|
API Key | This must indicate the Bearer authentication token to connect to the REST API. Default value is: <empty>
|
Timeout (in seconds) | This indicates how long the launcher will wait for a result from a keyword execution.
If the keyword execution has still a status equal to "CREATED" or "RUNNING" after this timeout has elapsed, the test is set as failed and the launcher will continue executing the next keyword.
Default value is: 3600 (1 hour)
|
These values can be changed while creating the campaign session from XStudio.
Process
With this launcher, the eTASQ Motion robot will execute the keywords as they are defined in the testcase's procedure.Each testcase has a procedure including one or more steps and checks. All are described as plain text and must match a keyword name and optionally some parameter values for this keyword.
Hence, it's pretty easy to describe a step or a check using the format:
<keyword name> - <parameter#1 name> = <parameter#1 value> - <parameter#2 name> = <parameter#2 value> ...For instance:
Sleep - time_ = 15sThe passed parameter values will automatically override the default values.