Configure tests - Examples

You can configure your tests by using test configuration parameters to set values. For basic information on the creation of test case parameters and configurations refer to see chapter "About test configuration parameters".

Example: file paths

An example for test configuration parameters is the definition of program paths in various operating systems. If you want to execute a test using both Windows XP and Windows 7, then various program paths must be stored.

Procedure

  1. Create the test configuration parameter Progpath for TestCase Test 3 in the TestCases section. For further information on how to create a test configuration parameter, refer to chapter "Create test configuration parameters ".

Test configuration parameter in TestCase

  1. Use the syntax C:\{CP[Progpath]}\TRICENTIS in the TestStepValue to link this with the configuration parameter Progpath.

Example for test configuration parameter

  1. Use TestCase Test 3 to create ExecutionLists for every operating system in the ExecutionLists section.

The test configuration parameter is copied to the ExecutionLists.

  1. Define the paths of the respective operating systems as values for the test configuration parameters.

Configuration parameter in the ExecutionList

Example: configure Appium

The following example shows an ExecutionList that has been configured and prepared for Appium on MobileLabs by using configurations. The example contains test configuration parameters that can be re-used. This allows you to make use of the tree structure of the configuration and the inheritance. If you execute the ExecutionList all defined test configuration parameters will be considered.

Procedure

  1. In the Configurations section, create the configuration Mobile. For further information on how to create a configuration, refer to chapter "Create configurations".

List of configurations in the Configurations section.

  1. Add the test configuration parameters AppiumServer, MobileLabsAccessKey and MobileLabsUsername to the new configuration and define the values as described in chapter "Specify TCPs for GigaFox (ex. Mobile Labs)".

    For further information on how to create a test configuration parameter, refer to chapter "Create test configuration parameters ".

Appium test configuration parameters added to a configuration.

  1. Add two new configuration as children to the Mobile configuration and name them iPad 9.7 and Android 7.0.

Device specific configurations added as child-configuration.

  1. The test configuration parameters that were defined on the Mobile configuration are inherited. Create a test configuration parameters on the Android 7.0 child-configuration and name it DeviceName. Define the new test configuration parameter DeviceName with the ID of the specific device in the Value column.

Test configuration parameter DeviceName is set on a child-configuration.

  1. Create an ExecutionList and name it Appium Engine - Android 7.0 (see chapter "Create an ExecutionList"). Drag the Android 7.0 configuration and drop it on the ExecutionList Appium Engine - Android 7.0.
    Once the configuration is linked to your Executionlist, the defined test configuration parameters will be considered during the next execution.

The configuration Android 7.0 is assigned to the executionlist Appium Engine - Android 7.0.

In this example an ExecutionList has been configured and prepared for Appium on MobileLabs by using configurations. From now on when executing the Appium Engine - Android 7.0 ExecutionList all the test configuration parameters, AppiumServer, MobileLabsAccessKey, MobileLabsUsername and DeviceName will be considered.