Configuring qualitia.properties

To execute test cases using Sauce Labs, you need to configure the qualitia.properties file accordingly. 

To execute the offline package using the Sauce Labs environment:

1. Open the qualitia.properties file from the config folder of the offline package.
2. Set xmlPath to the location where your test case execution XMLs (including Suite.xml and Map.xml) are stored.
3. Set LogPath to the folder where your you want to store your test cases results.Set
4. Do one of the following:
   1. If you are testing desktop application, set ExecutionEnvironment as sauce or
   2. If you are testing mobile application, set MobileExecutionEnvironment as sauce.
5. Set DefaultWebExecutionPlatform as follows:
   1. If you are testing desktop application, set it as Desktop or
   2. If you are testing mobile application, set it as Mobile

Image Removed

1. 1. .

Web Application Testing

When the Application under Test is a Web application and you want to execute the offline package in Sauce Labs environment, you need to configure the sauce.properties file accordingly.

To update the sauce.properties file:

1. Open the sauce.properties file.
2. Set properties "custom_username", "custom_accesskey" to valid values with reference to Sauce Lab's active user account.
3. Set "platform", "browser", and "version" to the corresponding OS, browser, and browser version you want your offline package to execute on.
   For example, if you want your offline package to execute on Internet Explorer 11 on OS Windows 8.1 then set the keys as follows:

• • platform=Windows 8.1
  • browser=Iexplore
  • version=11

Image Removed

Image Added

Mobile Application Testing

When the Application under Test is a mobile application and you want to execute the offline package in the Sauce Labs environment, you need to configure the saucemobile.properties file accordingly.

To update the saucemobile.properties file:

1. Open saucemobile.properties file.
2. Set properties "custom_username", "custom_accesskey" to valid credentials with reference to Sauce Lab's active user account.
3. Set "browserName", "deviceName", "platformVersion", "appiumVersion", "deviceOrientation" and so forth to corresponding browser, device, platform, Appium, and Orientation of device you want your offline package to execute on. For example, if you want to execute your offline package on Samsung Galaxy S4 Device that has Android 6.0 operating system using Appium version 1.6.4, then set keys as follows:
   • browserName=[Keep it blank for native application or specify the browser name for Web applications]
   • deviceName=Samsung Galaxy S4 Device
   • platformVersion=6.0
   • appiumVersion=1.6.4
   • deviceOrientation=Portrait

Users should not specify UDID when executing test cases on mobile devices on Sauce Labs.

4. Set the "custom_mobileAppPathType" as follows:

• When the application is to be uploaded from local drive, set it to Upload or
• When the application is to be taken from public URL such as Google Drive, DropBox, set it to PublicURL.

Once all the configuration settings are done successfully, you can now execute test cases on Sauce Labs.

Executing Offline Package

You can execute the offline package following the traditional method of offline execution.

For more information on execution of offline package, please refer to the Offline Package - Execution section.

Values you provide in the sauce.properties file can also be provided using command line. You can set the sauce properties using three different sources as mentioned below.

Viewing Current Execution on Sauce Lab's Dashboard

Once you have triggered the offline execution, you can view the status of your ongoing executions on the Sauce Lab's Dashboard. Each test case appears on dashboard as a single job with execution status against it. All the test cases are taken one by one by the sequence they are arranged in Suite. The status is updated after each test execution is completed on Sauce Lab environment with its status (fail / pass) against it. You can view the execution of test case clicking the current job on Dashboard.

You can record your test case execution configuring the sauce.properties file accordingly.

Set the recordVideo value as true and all the test case executions will be recorded.

You can download these videos once the test execution is completed from the Metadata tab. The video contains the execution of all the test cases available in Suite as the value set against QualitiaExecMode in the qualitia.properties file is PS (refers to per suite).

Execution Reports

Test execution reports are launched on the machine from where the execution was triggered after the test case execution is completed. You can also download the video of test case execution from the Metadata tab.

Execution of Tests Running Behind Firewall (on Private Networks)

Few applications are configured to be accessed using private networks. Such applications deny access when they are being accessed from other than local networks and so from Sauce Lab. Executing test cases on Sauce for such applications needs special configurations.

You need to execute the Sauce-Connectsc.jarexe file on the some machine in the private network to allow Sauce executing tests flawlessly.

Executing this sc.exe will create a tunnel allowing sauce to execute test cases in the private network. 

To execute applications of private network on Sauce:

1. Open the sauce.properties file from the config folder of Qualitia offline package.
2. Set the desired value for slw.tunnelIdentifier.
   The value set here for this key will be required when executing sc.exe in step 6. For more information on configuring this property, refer Sauce Labs documentation.
3. Download the Sauce connect zip Connect Proxy on any machine in the network using following url: 
   https://wiki.saucelabs.com/display/downloadsDOCS/Sauce-Connect-3.1-r32.zipUnzip the +Connect+Proxy
4. Extract the folder at the suitable location.
   You will find the sc.exe file in the bin folder.
5. Open Command Prompt and navigate to the Sauce-connect.jar file followed by Sauce Username and Access key.
   For example, <Location of the jar file>java -jar Sauce-Connect.jar parvinm ab8fa4d8-8c1f-4904-8353-b6074fc744fb
6. Press the Enter button.

1. folder where sc.exe file exists. 

2. Enter the following command.

   Code Block
   theme Midnight
   sc -u <sauce_username> -k <accesskey> -i <tunnelID> For example: sc -u john.doe -k 8becc95c-4559-4582-a617-7d38544797a2 -i tunnel-1232

   
   

3. Press Enter.

Once the SC.exe file is executed successfully, you can execute your Offline offline tests on Sauce environment using the same method mentioned above.

Image Removed

Execution using Browser Capabilities

You can also execute test cases on remote environment using selenium supported Browser Capabilities.

For more information on this, please refer to the Execution using Browser Capabilities section.

Executing Test Cases on iOS Devices

If you are executing test cases on iOS mobile devices using Sauce Labs, you need to configure settings in the iosdc.properties file accordingly.

• If iOS device is 9.3.x and below, automationname should be Appium or
• If iOS device is 10.0.x and above, automationname should be XCUITest.

Execution using W3C Protocols

W3C-compliant Selenium capabilities and protocol is supported for test case executions in the Sauce Labs environment with selenium v3.11.0 and above.

This W3C protocol is supported while executing test cases using following browser versions:

• Internet Explorer v11 and above,
• Mozilla Firefox v53 and above, and
• Google Chrome v 61 and above.

You'll need to make a few changes to the desired capabilities in the sauce.properties file to execute your existing Qualitia test cases using these new W3C capabilities.

Here is the list of capabilities which you need to modify when you want to execute test cases using W3C protocol. 

slw.useW3C=True
browser=Firefox, Chrome, or Internet Explorer)
version=(for firefox, 53 and above, for chrome 61 and above, for IE 11 and above)
seleniumVersion=3.11.0

For more information about executing test cases using W3C-Protocols and Capabilities, refer to the Sauce Labs documentation.