More configuration options¶
For every app configuration you can additionally specify several global options.
Open app override test¶
Often you will want to override the default Open App action with your own. For example when instrumenting a generic HTML app you could add a "click-through" sequence that would visit the device portal and open the application.
Open app override field in the app configuration allows you to specify a dedicated Suitest test that will be executed when the open app operation is about to be executed in your other tests.
Configuration variables¶
Suppose that you have an app deployed on staging (server) and preprod
(pre-production). On staging, it has an address staging.example.com
and on
preprod, preprod.example.com
. If you encapsulate this difference in a
variable, you will be able to use the same test cases for both preprod and
staging environments.
Configuration variables can be used anywhere within the Test editor and JavaScript API, including timeouts, counters, element properties etc.
Continuing with the above-mentioned example in both staging and preprod
configuration, create a variable called url
and use <%url%>
to call the
variable from within the test:
You can define as many variables as needed. Suitest will warn you when you try to run a test that references an unknown variable.