Qualitia users can provide arguments based on the execution environments or make changes to the properties file to use the QualitiaOffline jar file to execute in different test environments.

Supported Environments and Configurations

Qualitia Offline Package is compatible to execute on Sauce Labs and Remote environments along with local environments. Depending on the desired environment the Qualitia.Properties file accommodates configurations as follows:

Supported Platforms and Browsers

Qualitia Offline Package supports multiple platforms and browsers for test case executions and report viewing. Browser and platform support can be classified in two ways:

• Support for Execution
• Support for Report Viewing

Supported Browsers and Platforms for Offline Executions

Here is a quick overview of the browsers and platforms you can use for test executions using offline package.

Local					Remote
	IE	Firefox	Chrome	Safari	IE	Firefox	Chrome	Safari
Windows
Linux
Mac

Executions on Virtual Machines:

BrowserStack					Sauce Labs
	IE	Firefox	Chrome	Safari	IE	Firefox	Chrome	Safari
Windows
Linux
Mac

Supported Browsers and Platforms for Report Viewing

Once test cases are executed, Qualitia displays reports using Internet Explorer (IE) browser on the local machine from where the execution is triggered. Following is the quick overview of the supported browsers that can be used for viewing reports on different platforms.

Chrome is not supported for report viewing.

	IE	Firefox	Chrome	Safari
Windows
Linux
Mac

Offline Execution in Local Environment

The offline package can be executed in local environments exactly as it is executed traditionally. Change the ExecutionEnvironment value as local in the qualitia.properties file and start executing it.

To change configuration settings for executing tests in local environment:

1. Open the config folder of offline package.
2. Open qualitia.properties file using Notepad++.
3. Set the ExecutionEnvironment value as local.
   All the other configuration settings in the qualitia.properties file have to be done traditionally.

Offline Execution and Report

You can execute offline package using the traditional method after the configuration settings are done.

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

It uses browsers available on local machine for test case executions. For example, if you have chosen "Firefox" to be the execution browser and the local machine has Firefox v42, Qualitia continues execution using Firefox v42. After the execution is complete, test execution reports are displayed on the local machine.

Execution using Browser Capabilities

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

For more information about executing test cases using browser capabilities, please refer to the section Execution using Browser's Capabilities

Offline Execution on Remote/Distributed Environment

You can execute the test cases using offline package after configuring settings accordingly. This gives you provision to trigger suite execution using any machine in the network. You do not need to move the offline package to different machines to execute it. You can do it in following two ways;

• Normal Remote Execution
• Remote Execution through Selenium Grid

Normal Remote Execution

This option can be used when you are aware of the remote machine details where you wish to execute your test cases. Please note that here you choose to execute Offline Package on a remote machine with specific details.

Qualitia uses the selenium-standalone-server-jar for test case executions on the target remote machine.

To run selenium-stand- alone jar:

1. 1. Download the selenium-standalone-jar on the target machine where you want to execute test cases.
   2. Download the drivers corresponding to the offline execution browser (chromedriver, IEdriverServer, and so on) and store it in the same location where the selenium-stand-alone-jar is saved.
   3. Open the Command Prompt window and navigate to the location where jar is stored.
   4. Do one of the following:

      • If the execution browser is Iexpore and selenium sever standalone version is 2.xx.x, execute following command: java -jar selenium-server-standalone-2.45.0.jar - Dwebdriver.ie.driver="D:\Data\Testing\Apps\IEDriverServer.exe".
        

         View Image

        

      • If the execution browser is Iexpore and selenium sever standalone version is 3.xx.x, execute following command: java -Dwebdriver.ie.driver="D:\Data\Testing\Apps\IEDriverServer.exe" -jar selenium-server-standalone-3.0.1.jar
        

         View Image

        

Configuration Settings

Once you download Selenium-stand-alone jar and browser drivers, you need you change some settings in the qualitia.properties file in order to run Normal Remote Execution.

To configure settings as for Normal Remote Execution:

1. Open the qualitia.properties file from the config folder of offline package.
2. Set the ExecutionEnvironment value as remote.
3. Set the RemoteURL value to a valid remote URL that is IP and port of remote machine.

For example: RemoteURL=http://192.168.25.123:4445

Offline Remote Execution and Reports

You can execute offline package using the traditional method after the configuration settings are done.

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

It uses browsers available on local machine for test case executions. For example, if you have selected "Firefox" as an execution browser and the local machine has Firefox version 42, Qualitia continues execution using Firefox version 42. Execution Reports are displayed on the local machine after executing the test cases.

Execution using Browser Capabilities

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

For more information about executing test cases using browser capabilities, please refer to the Execution using Browser's Capabilities section. 

Mobile Test Case Executions

In order to execute mobile test cases on the remote machine, make sure that Appium server is up and running on the designated remote machine.

For more information about installing Appium Server, refer to the Qualitia Online Help.

Remote Execution through Selenium Grid

You can choose this option when you have distributed test environments where you want network to select a remote machine based on the availability.

Key Points to Know Before You Start

In order to perform remote execution through selenium grid, you need to configure Hub and Node in the network.

Creating Hub in the Network

A Hub can be created in the network following the steps mentioned below.

1. Decide a machine in the network to register as hub (with IP, for example, 192.168.25.6).
2. Download the Selenium-server-standalone jar file on Hub machine.
3. Open Command Prompt and navigate to the location where Selenium-server-standalone-jar is saved.
4. Execute command "java -jar selenium-server-standalone-2.xx.0.jar-role hub -port 4445".

Create Node and Register to Hub

Once hub is created in the network, you can select multiple machines to act as its nodes.

Registering nodes include following steps.

1. Download the Selenium-server-standalone jar file on Hub machine.
2. Launch the command prompt and navigate to the location where Selenium-server-standalone jar file is saved.
3. Execute command "java -jar selenium-server-standalone-2.xx.x.jar -role node–hub http://hubIP:4445/grid/register".

Configuration Settings

Before executing test cases in remote execution in Selenium grid, you need to configure settings accordingly.

Here are some important points to keep in mind when configuring settings for remote execution in selenium grid.

• Selenium server jar version used in Qualitia offline package and downloaded at remote machines including Hub and Nodes should be same all over.
• Java needs to be installed and configured in computer's environment path.
• Port number used for hub is changeable and default port number is 4444.
• As hub selects node for execution at its own at run time, you cannot provide details for specific OS / Platform.
• To know more about how to setup Selenium grid hub and node it is recommend using the selenium grid links given below
  • https://github.com/SeleniumHQ/selenium/wiki/Grid2+_
  • http://www.joecolantonio.com/2014/10/07/selenium-grid-how-to-setup-a-hub-and-node/+_

To configure settings for remote execution in selenium grid:

1. Open the qualitia.properties file from the config folder of offline package.
2. Set the ExecutionEnvironment value as remote to inform qualitia-offline.jar that offline package has to be executed on a remote machine.
3. Set the RemoteURL value to a valid remote URL that is IP and port of remote machine. For example: RemoteURL=http://192.168.25.123:4445

Offline Remote Execution and Reports

You can execute offline package using the traditional method after the configuration settings are done.

For more information about executing Offline package, please refer to the Offline Package - Execution section. 

It uses browsers available on local machine for test case executions. For example, if you have selected "Firefox" as an execution browser and the local machine has Firefox version 42, Qualitia continues execution using Firefox version 42. Execution Reports are displayed on the local machine after executing the test cases.

Execution using Browser Capabilities

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

For more information about executing test cases using browser capabilities, see section 3.4.5, "Execution using Browser's Capabilities."

Mobile Test Case Execution on Nodes

In order to execute mobile test cases using selenium grid, make sure that Appium server is up and running on the designated node.

For more information about installing Appium Server, refer to the Qualitia Online Help.

Offline Execution on Sauce Labs

The Sauce Labs is cloud environment which allows users to run tests in the cloud using different combinations of operating systems, browsers, and browser versions. In this environment all tests are executed on Sauce Labs VM. You can view the ongoing suite execution on Sauce Lab's Dashboard.

It is recommended to set ScreenCaptureMode value as Browser when the execution environment is Sauce or Remote.

You can set the value for FailStepOnBrowserScreenshotFailure as per the test case requirements (as true or false) to behave when the application under test generates any run-time Alert / Windows.

To know more about Sauce Labs click here.

Prior starting offline execution on Sauce Labs, ensure you have;

• An active account with valid user name / password and
• Sufficient balance of execution hours.

Configuration Settings

In order 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 offline package.
2. Set ExecutionEnvironment as Sauce.
3. 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

When the Application under Test is desktop 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 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 keys as follows:

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

When the Application under Test is 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 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 on Firewall Applications

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-Connect.jar file on the machine in the private network to allow Sauce executing tests flawlessly.

To execute applications of private network on Sauce:

1. Download the Sauce connect zip on any machine in the network using following url: https://saucelabs.com/downloads/Sauce-Connect-3.1-r32.zip
2. Unzip the folder.
3. 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
4. Press the Enter button.

Once the Sauce-Connect.jar file is executed successfully, you can execute your Offline tests on Sauce environment using the same method mentioned above.

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's 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.

Offline Execution on BrowserStack

BrowserStack is a cloud environment that allows running tests in the cloud using different combinations of operating systems, browsers, and browser versions. In this environment, all tests are executed on BrowserStack VM. You can view the ongoing tests execution on BrowserStack.

For more information about BrowserStack, click here.

Before you start offline execution on BrowserStack, ensure you have:

• An active account with valid Username/Access Key and
• Sufficient balance of execution hours

Configuring qualitia.properties and browserstack.properties

In order to execute test cases on BrowserStack, you need to configure the qualitia.properties file accordingly.

To execute the offline package on the BrowserStack environment:

1. Open the qualitia.properties file from the config folder of offline package.
2. Set ExecutionEnvironment as browserstack.

Once the qualitia.properties file is updated, you must configure the browserstack.properties file in order to execute offline package in the BrowserStack environment.

To update the browserstack.properties file:

1. Open the browserstack.properties file.
2. Set properties "custom_username", "custom_accesskey" to valid values with reference to BrowserStack's active user account.
3. Set "OS", "OS_Version", "browser", and "version" to the corresponding OS, browser, and browser version that you want your offline package to execute on.

For example, if you want your offline package to execute on Windows 10, Internet Explorer 11 then set keys as follows:

• OS=Windows
• OS_Version=10
• browser=iexplore
• version=11

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

Executing Offline Package

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

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

Values you provide in the browserstack.properties file can also be provided using the Command Prompt window. You can set the BrowserStack properties using three different sources as mentioned below.

Viewing Current Execution on BrowserStack

Once you have triggered the offline execution, you can view the status of your ongoing executions on BrowserStack. BrowserStack considers each Test case as a new project. The status is updated after each project is completed with its status against it. Also, you can filter the projects by their status (Completed, Timeout, or Errors) or you can search it by build name or session name.

You can record your test case execution configuring the browserstack.properties file accordingly. If you 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.

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 view the browser type and browser version on the report displayed.

Execution of Tests Running Behind Firewall Applications

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

When executing test case for applications running behind firewall on Windows, you need to execute the BrowserStackLocal.exe file on the machine in the private network to allow BrowserStack to execute tests flawlessly.

To execute test cases for applications running behind firewall on BrowserStack (Windows):

1. Make sure you have set the browserstack.local value as true in the browserstack.properties file.
2. Download the BrowserStackLocal.exe on any machine in the network using the following url:
   https://www.browserstack.com/automate/python#setting-local-tunnel
3. Unzip the folder.
4. Open Command Prompt and navigate to the BrowserStackLocal.exe file followed by BrowserStack Access key.
   For example:
   <Path where the file is saved> BrowserStackLocal.exe --key <BrowserStack access key>
5. Press Enter.

Once the BrowserStackLocal.exe file is executed successfully, you can execute your Offline tests on BrowserStack environment using the same method mentioned above. When executing test case for applications running behind firewall on Mac, you need to execute the BrowserStackLocal Unix Executable file on the machine in the private network to allow BrowserStack executing tests flawlessly.

To execute test cases for applications running behind firewall on BrowserStack (Mac):

1. Make sure you have set the browserstack.local value as true in the browserstack.properties file.
2. Download the BrowserStackLocal Unix Executable file on any machine in the network using the following url:
   https://www.browserstack.com/automate/python#setting-local-tunnel
3. Unzip the folder.
4. Open Terminal and navigate to the BrowserStackLocal Unix Executable file followed by BrowserStack Access key.
   For example:
   ./BrowserStackLocal --key <BrowserStack access key>
5. Press Enter.

Once the BrowserStackLocal Unix Executable file is executed successfully, you can execute your Offline tests on BrowserStack environment using the same method mentioned above.

Execution Using Browser Capabilities

You can also execute test cases on remote environment using Selenium supported Browser capabilities.

For more information about this, please refer to the Execution using Browser's Capabilities section.

Execution using Browser's Capabilities

Selenium allows you setting desired browser specific properties to be used when executing test cases. These properties can be set for offline execution as well. You can provide these browser specific details through browser-capability files. For each supported browser (Firefox, IE, Google Chrome, and Safari) there is a separate property file present in the Config folder of Qualitia's offline package. Following is the list of files;

• firefoxdc.properties
• googlechromedc.properties
• iexploredc.properties
• safaridc.properties

Each property file above is a set of all the browser specific properties that Selenium allows you change. If you do not change any property, Selenium uses its default values.

Changing Browser Capabilities:

Selenium uses its own settings for each key that has been commented in the file, except unexpectedAlertBehaviour. Changing properties here overrides the values provided in qualitia.properties / sauce.properties, or selenium's default values. When executing test cases using offline package, you can change some property values providing command line arguments accordingly. But all capability keys do not accept values from command line, hence it is recommended providing values through property files.

To change browser capabilities:

1. Open the browserdc.properties file from the config folder of offline package.
2. Locate the value you want to change in the file.
3. Remove the # sign located prior to the capability.
4. Enter the value you want to set for the capability.

For example; if you want to change the version of the browser to be used for test execution, remove the # sign located prior to the version and enter the version number against it.

Qualitia gives you provision to set these values for Selenium. Selenium has its own control on what value to use and how to reflect them in Execution Browser. For more information about Selenium Capabilities, refer following links:

https://code.google.com/p/selenium/wiki/DesiredCapabilities

https://sites.google.com/a/chromium.org/chromedriver/capabilities

Reports

Execution reports display OS and Browser with their corresponding versions on its summary page along with the execution environment used. For example, if you have chosen execution as Sauce and execution browser as Firefox 42 on Windows 8.1 report is displayed as follows;

Limitations of Remote/Sauce Executions

When using Qualitia Offline Package on the Remote and Sauce environments, following are the limitations users face when executing test cases.

Lack of Support for Java Robot Based Actions:

Sauce does not support Java robot based actions when executing test cases. Hence following actions do not get executed in Sauce and Remote environment;

• AttachFile
• DownloadFile
• WindowsAuthentication
• PressKeys

Lack of support for java robot based actions on Sauce / Remote environment fails the test case executions.

In order to overcome this problem, you need to validate the test cases that have java based robot actions as mentioned above and;

• either execute them in local environments or
• create their AutoIt scripts to be executed in Sauce environment.

For more information about support for AutoIt, please refer to the Support for AutoIT in Sauce Execution Environment section.

Lack of Support for Headless Mode:

Sauce execution environment does not support the Headless mode.

For parallel execution in Sauce, you can execute tests in multiple VMs. A separate VM is allocated to execute each offline package, so you can run multiple offline packages to get multiple VMs.

User Defined Firefox Profile:

Executing test cases in Sauce environment using user defined Firefox profile is experimental.

Support for AutoIT in Sauce Execution Environment

In order to achieve execution of Windows based actions such as DownloadFile, PressKeys, WindowsAuthentication, and so on, Qualitia supports Sauce's "Pre-Run" feature. It allows uploading AutoIT.exe (or any exe) and running before starting test case executions. Running .exe performs the windows based actions flawlessly.

In order to achieve this, you need to set following properties in the Sauce.properties file.

• custom_use_prerun: This option decides whether to use Pre-Run feature or not. Set it as true to run the Pre-Run feature.
• custom_exe_name: This contains the exe file name to be executed in Sauce environment. To run exe in Sauce, you must upload the file to Sauce network.
• args: It is the list of command line parameters that you want to execute.
• custom_use_upload: This option decides whether to upload file in Sauce network or not. Set it as true to use upload related properties.
• custom_file_path: Set this to the valid path where the file is located to be uploaded in the Sauce network.
• Same way set all other properties for pre-run and uploading script file.
• For more information about the Pre-Run feature operation, please refer following links,

https://wiki.saucelabs.com/display/DOCS/Test+Configuration+Options#TestConfigurationOptions-Pre-runExecutables (pre-run)

https://wiki.saucelabs.com/display/DOCS/Temporary+Storage+Methods (upload)