Introduction

While creating an Execution, we need to create at least one Execution Configuration inside it for it to be Executable.


The Execution Configuration is mandatory because the Execution merely outlines the set up of the Test Execution along with some trivial configuration. It is the Execution Configuration which specifies the actual Environment details where the Tests are to be run.


We can make more than one Execution Configuration in the Execution page so that the Tests are run simultaneously on multiple Environments. This is useful for parallel Executions and Cross-Browser Testing.


Navigation


The Create Execution Configuration page is presented while creating/Editing an Execution. We can get to the Executions page as follows:



Project > Applications > Versions > Executions



Note: Before Creating an Execution, we need one or more Test Cases that are to be executed and a Test Suite to group those Test Cases.


You can either select one of the already created Execution in the Executions page or create a new Execution as follows:


Clicking on one of the already created Execution will take us to the Execution Details page. Under Environments sections, click on the Create Execution Configuration button to open the Create Execution Configuration page.


If you are creating an Execution, click on the Create button in Executions page to open Create Execution page. Under Environments sections, click on the Create Execution Configuration button to open the Create Execution Configuration page.


Create Execution Configuration


The Create Execution Configuration page looks as given below:

Note: The above-given image is the Create Execution Configuration page of a Web Application. Additional fields are present for other Application Types as given below.



Enter the details as given below:


Title: Enter a title to identify the environment.


Machine*: Select the local machine on which tests are to be executed

Note: For hybrid execution model, we need to add your local test machine details before creating an execution. Refer this help document to add a Test Machine for execution in Hybrid model.


Operating System: Select the Operating System(OS) in which you want to execute the tests.


OS Version: Select the Operating System version in which you want to execute your tests.


Browser: Select the browser in which you want to execute your tests


Browser Version: Select the version of the selected browser in which you want to execute your tests.


Testobject API Key*: The API access key used for authentication of Sauce Labs account.


Appium URL*: Enter the Appium Server IP Address for the instance of Appium Server started on your local machine.

Please check the following article for more details on Appium Setup and getting the Appium URL - How to configure Appium Desktop for automating Mobile Apps?


And Here's the official guide to Getting started with Appium Desktop.


Device Name*: Enter the Serial number of the Android device on which tests are to be performed.

You can get the Serial number of the Android device using ADB if ADB is configured on your Machine.

Here's an article to setup ADB on your machine


UDID*: Enter the unique UDID for the cloud iOS device that you are going to use for testing.

Here's a simple utility website to find your UDID - http://get.udid.io/


Select one of the methods for locating the mobile application to be tested:

(For Android Native)

  • Use APK

    • APK Path: Enter the path to the apk file of the application.

  • App Details

    • App package: The name of the Android app package that is to be tested. This is the formal identifier of an app. Refer this help document for more details on finding the app package and app activity names for the application to be tested.

    • App activity: If you want the testing process to be done on a specific activity(application screen) inside the app, you can specify the activity name in this option.

  • Use Uploads

    • App Name: Select the Application file uploaded to the Testsigma Cloud by name.


(For iOS Native)

  • Bundle ID

    • Bundle ID: Enter the Bundle ID for the iOS application that you are going to test.

                    Note: Bundle ID / App ID is a unique identifier for an iOS application or a group of iOS applications.

  • App Path

    • Use IPA: Enter the path to the IPA file of the application.

  • Use Uploads

    • App Name: Select the Application file uploaded to the Testsigma Cloud by name.


APK Path*: Enter the path to the APK file of the application.


Use IPA*: Enter the path to the IPA file of the application. (Only for iOS native)


Mandatory Steps Only: Check this option if you want to run only the Test Steps marked as mandatory in each Test Case.


Test Suite List: Select one or more Test Suites(listed on the right side) to execute in the selected test environment.


Environment Parameters: Select the environment parameter from the available list. This is required only if you have used Environment Parameter test data in Test Steps. Refer this help document for more details on Environment Parameter test data.



Note: * denotes that these options are specific to certain Execution Models and might be unavailable for others.



After entering the details, select the Test Suites to be included in this Execution Configuration and click Create button to Create the Execution Configuration.


You will be taken to the Create Execution page and you can configure additional settings there before creating the Execution.



Click on the Create Execution Configuration button again if you need to create more environments.


Edit Execution Configuration


As we discussed earlier, clicking on one of the already created Executions in the Executions page will take us to the Execution Details page.


Under Environments sections, you can see the available Execution Configurations.



Click on the Edit button beside the Configuration name to open the Edit Execution Configuration page.


Make necessary changes and click on Update button to finalize the changes.


Delete Execution Configuration

Navigate to the Executions page and click on the Execution name under which the Execution Configuration to be deleted is located.


As discussed earlier, we can see the Execution Configuration under the Environments section in the Execution details page.


1. Click on the Delete button beside the Configuration name to open the confirmation dialogue.



2. Select the checkbox and click on the Delete button to confirm the deletion.


The Configuration will be deleted and we will be taken back to the Execution details page.


Note: Testsigma mandates at least one Execution Configuration in an Execution for it to be runnable. Please maintain at least one Execution Configuration in the Execution if you want to run it.