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 Samsung Tizen app or a general 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.

Example overriding the *Open app* action for a Samsung Tizen application in order to achieve fully automated app opening
Example overriding the Open app action for a Samsung Tizen application in order to achieve fully automated app opening

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.

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:

Example using variable to refer to a URL. The test scenario does no longer depend on the app URL, because it is a parameter of configuration. So we can apply this test without modification to different app versions and environments
Example using variable to refer to a URL. The test scenario does no longer depend on the app URL, because it is a parameter of configuration. So we can apply this test without modification to different app versions and environments
Variables can be used anywhere in the test.
Variables can be used anywhere in 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.