Introduction

Qualitia provides its own set of system variables that let you decide test case or task execution flow at run time. Qualitia System Variables act as global variables and can be accessed in any test case. You can only use the values of these variables, but cannot modify those in any test step. Data type of these variables can be integer, Boolean, and string values. Following is the complete list of System Variables that can be used when developing test cases in Qualitia:

$$_STATUS

This system variable records and stores value of the status of the last executed step.

You can then add tasks in the test cases to be executed based on the recorded value.

Value of this variable is not case-sensitive. 

Possible values for relational operator of $$_STATUS variable are as follows:

$$_IS_WEB_EXECUTION_PLATFORM_DESKTOP

This system variable stores a Boolean value for current desktop web execution platform. 

This expression returns Boolean value comparing the values set in Configuration Settings (or the value overridden by the action SwitchWebExecutionPlatform).

• If the current web execution platform is set as Desktop, returns as TRUE.
• If the current web execution platform is set as Mobile, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

Example:

This variable can be used where user wants to execute certain test steps based on the execution platform (Mobile and Desktop).

$$_IS_WEB_EXECUTION_PLATFORM_MOBILE

This system variable stores a Boolean value for current mobile web execution platform. 

This expression returns Boolean value comparing the values set in Configuration Settings (or the value overridden by the action SwitchWebExecutionPlatform).

• If the current web execution platform is set as Mobile, returns as TRUE.
• If the current web execution platform is set as Desktop, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

Example:

This variable can be used where user wants to execute certain test steps based on the execution platform (Mobile and Desktop).

$$_ISANDROID

This system variable stores a Boolean value for Android mobile platform.

This expression returns Boolean value comparing the values set in Configuration Settings (Mobile).

• If Platform under configuration settings is set as Android, returns as TRUE.
• If Platform under configuration settings is set as iOS, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the operating system (OS) of the execution device / emulator is Android. Once the OS is identified, tasks can be added to be executed accordingly.

$$_ISIOS

This system variable stores a Boolean value for iOS mobile platform.

This expression returns Boolean value comparing the values set in Configuration Settings (Mobile).

• If Platform under configuration settings is set as iOS, returns as TRUE.
• If Platform under configuration settings is set as Android, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the operating system (OS) of the execution device / simulator is iOS. Once the OS is identified, tasks can be added to be executed accordingly.

$$_ISWINDOWS

This system variable stores a Boolean value for Windows platform. This is generally used when executing test cases using Offline Package.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If platform is Windows, returns as TRUE.
• If platform is not Windows, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the operating system (OS) of the execution device is Windows. Once the OS is identified, tasks can be added to be executed accordingly.

$$_ISLINUX

This system variable stores a Boolean value for Linux platform. This is generally used when executing test cases using Offline Package.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If platform is Linux, returns as TRUE.
• If platform is not Linux, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the operating system (OS) of the execution device is Linux. Once the OS is identified, tasks can be added to be executed accordingly.

$$_ISMAC

This system variable stores a Boolean value for Mac platform. This is generally used when executing test cases using Offline Package.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If platform is Mac, returns as TRUE.
• If platform is not Mac, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify the execution device is Mac. Once this is identified, tasks can be added to be executed accordingly.

$$_ISFIREFOX

This system variable stores a Boolean value for Execution browser type.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If Browser Type under configuration settings is set as Firefox, returns as TRUE.
• If Browser Type under configuration settings is set as other than Firefox, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the test case execution browser is set as Firefox. Once the browser is identified, tasks can be added to be executed accordingly.

$$_ISCHROME

This system variable stores a Boolean value for execution browser type.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If Browser Type under configuration settings is set as Google Chrome, returns as TRUE.
• If Browser Type under configuration settings is set as other than Google Chrome, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the test case execution browser is set as Google Chrome. Once the browser is identified, tasks can be added to be executed accordingly.

$$_ISIE

This system variable stores a Boolean value for execution browser type.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If Browser Type under configuration settings is set as Internet Explorer, returns as TRUE.
• If Browser Type under configuration settings is set as other than Internet Explorer, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the test case execution browser is set as Internet Explorer. Once the browser is identified, tasks can be added to be executed accordingly.

$$_ISSAFARI

This system variable stores a Boolean value for execution browser type.

This expression returns Boolean value comparing the values set in Configuration Settings.

• If Browser Type under configuration settings is set as Safari, returns as TRUE.
• If Browser Type under configuration settings is set as other than Safari, returns as FALSE.

 The value returned (TRUE or FALSE [case-sensitive]) can be used when developing test cases using Automation studio.

This variable can be used to verify that the test case execution browser is set as Safari. Once the browser is identified, tasks can be added to be executed accordingly.

$$_MOBILE_APP_PATH_TYPE

This variable is used by Qualitia only when developing test cases for executing offline packages on Sauce Labs. You can use this variable to change the application path type (Upload or PublicURL) at test case level. 

When executing offline package for mobile applications on Sauce Labs, Qualitia gives provision to upload application under test either from local (or shared) location to Sauce Storage or make it available to Sauce using the public URL.

To use this variable, the user must store the application path type using the StoreVariable action as shown in the screenshot below before using the Mobile.OpenApp action.

As shown in the screenshot above, the key name in the StoreVariable action must be "$$_Mobile_APP_PATH_TYPE" and the value of this key should either be Upload or PublicURL.   

Based on the value set in variable, Qualitia uses the app path type at test case level when executing offline packages in Sauce Labs environment.

• When set as Upload, application file is uploaded into Sauce Storage.
• When set as PublicURL, application file is taken by Sauce Labs using PublicURL.

In both the cases, it is mandatory for user to give the absolute path to the application in the Mobile.OpenApp action parameter. 

$$_HTTP_STATUS

This variable stores the HTTP request status when executing SOAP and REST API actions in Qualitia. You can use this value to form the test case flow based on your requirements.

$$_HTTP_HEADERS

This variable stores the HTTP headers after executing SOAP and REST API actions with Qualitia. You can use the values from the header to form the test case flow based on your requirements.

$$_HTTP_REPONSE_TIME

This variable stores the time taken to get the HTTP response. You can use this value to form the test case flow based on your requirements.