Qualitia Client and Offline Package supports test suite executions on multiple platforms and browsers for test case executions and report viewing. Along with the local machines, test suite can be executed through Qualitia Client and Offline package on remote o cloud environments.
...
Qualitia uses the selenium-standalone-server-jar for test case executions on the target remote machine.
To run selenium-stand- alone jar:
Download the selenium-standalone-jar on the target machine where you want to execute test cases.
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.
Open the Command Prompt window and navigate to the location where offline jar is located.
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”.
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
...
Do one of the following:
To execute from a Qualitia client, open the associated execution profile.
To execute an offline suite, do the following in the order listed:
Open the offline package folder.
From the Configuration Manager folder, and double-click the Qualitia Offline Configuration Manager.
Do one of the following;
Click Browse next to Select the Suite Directory, and then locate and select the offline suite.
Enter the location path of the offline suite folder, and press Tab.
Under the Select the profile to edit, select the execution profile created to execute on remote environment.
Select the associated execution profile that is defined to execute on remote environment.
From the Mapped Execution Profile list, select the execution profile you have opened.
Set the ExecutionEnvironment as Remote.
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/wd/hubClick Save.
Suite Execution
...
Download the Selenium-server-standalone jar file on the node machine.
Launch the command prompt and navigate to the location where Selenium-server-standalone jar file is saved.
Execute command "java -jar selenium-server-standalone-2.xx.x.jar -role node –hub http://hubIP:4445/grid/registerr".
| Note |
|---|
You can bundle your IEServerDriver.exe, Geckodriver.exe, or ChromeDriver.exe running while registering to Hub. |
...
Selenium server jar version used in Qualitia offline package and downloaded at remote machines including Hub and Nodes must be the same all over.
Java needs to be installed and configured in the computer’s environment path.
Port number used for the hub is changeable and the default port number is 4444.
As hub selects a 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, you recommend using the Selenium grid links given below.
Either you can create an execution profile to execute on the remote environment or edit an existing execution profile. For more information, refer to Working with Execution Profiles.
...
Do one of the following:
To execute the test suite from a Qualitia client, open the associated execution profile.
To execute the offline suite, do the following in the order listed:
Open the offline package folder.
From the Configuration Manager folder, and double-click the Qualitia Offline Configuration Manager.
Do one of the following;
Click Browse next to Select the Suite Directory, and then locate and select the offline suite.
Enter the location path of the offline suite folder, and press Tab.
Under the Select the profile to edit, select the execution profile created to execute on remote environment.
Select the associated execution profile that is defined to execute on remote environment.
From the Mapped Execution Profile list, select the execution profile you have opened.
Set the ExecutionEnvironment as Remote.
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/wd/hubSet the GridPlatform value to a valid platform where you want to execute test cases. For example: Set the GridPlatform=Win10.
Click Save.
...
Either you can create an execution profile to execute on the remote environment or edit an existing execution profile. For more information, refer to Working with Execution Profiles.
Before you execute a test suite, ensure that all the nodes in the network meets the minimum system requirements. For more information, refer to Requirements and Configuration Settings for Mobile Environments.
...
Do one of the following:
To execute the test suite from a Qualitia client, open the associated execution profile.
To execute the offline suite, do the following in the order listed:
Open the offline package folder.
From the Configuration Manager folder, and double-click the Qualitia Offline Configuration Manager.
Do one of the following;
Click Browse next to Select the Suite Directory, and then locate and select the offline suite.
Enter the location path of the offline suite folder, and press Tab.
Under the Select the profile to edit, select the execution profile created to execute on remote environment.
Select the associated execution profile that is defined to execute on remote environment.
From the Mapped Execution Profile list, select the execution profile you have opened.
Configure the settings in the associated execution profile. For more information, refer to Requirements and Configuration Settings for Mobile Environments.
Set the ExecutionEnvironment as Remote.
Set the RemoteURL value to a valid remote URL that is IP and port of the remote machine.
For example: RemoteURL=http://192.168.25.123:4445
Set the GridPlatform value to a valid platform where you want to execute test cases. For example: Set the GridPlatform=Win10.
Click Save.
...
For more information about BrowserStack, click here.
Before you start offline execution on BrowserStack, ensure you have:
...
| Info |
|---|
BrowserStack does not support all Selenium versions. Qualitia users can use the browserstack.selenium_version capability to specify the version they want to use when executing test cases. |
Mandatory Settings in Qualitia
...
From the Environment list, select Cloud.
From the Cloud Platform list, select BrowserStack.
Select the Edit Desired Capabilities checkbox.
Select or enter the following values:
Url
username
accesskey
Additional Recommendations:
On the Execution Parameters tab, select ScreenCaptureMode as Browser.
Viewing Current Execution on BrowserStack
...
Make sure you have set the browserstack.local value as true in the Edit Additional capabilities.
Download the BrowserStackLocal.exe on any machine in the network using the following url:
https://www.browserstack.com/automate/python#setting-local-tunnelUnzip the folder.
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>Press Enter.
...
Make sure you have set the browserstack.local value as true in the Edit Additional Capabilities.
Download the BrowserStackLocal Unix Executable file on any machine in the network using the following url:
https://www.browserstack.com/automate/python#setting-local-tunnelUnzip the folder.
Open Terminal and navigate to the BrowserStackLocal Unix Executable file followed by BrowserStack Access key.
For example:
./BrowserStackLocal --key <BrowserStack access key>Press Enter.
...
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:
Execution on Sauce Labs
Introduction
...
To know more about Sauce Labs click here.
Also, before uploading an iOS native or hybrid application, ensure that you build the application by following the below Saucelabs guidelines:
...
An active account with valid user name / password
Sufficient balance of execution hours.
| Info |
|---|
After logging to Sauce Labs, click Data Center located at the top-right corner, and select the Time Zone to USE West 1. |
Mandatory Settings in Qualitia
...
Url
username
accesskey
For testing on a desktop web application, select usew3c as True.
For testing on a mobile application,
Enter the Platform Version only and do not edit the default value for the Native Object sync time.
Do not add the same capabilities that are already specified in Sauce labs Mobile section, such as deviceName.
For iOS mobile application, ignore value present in Appium Server URL as it is mandatory field. It is not used in the execution.
For testing on a mobile hybrid application, select nativeWebScreenshot as True.
For testing on an iOS native or hybrid application, perform the following actions:
From the automationName drop-down, select XCUITest.
Enter the latest Appium version number as the appiumVersion.
Additional Recommendations:
In the Execution Parameters tab, select ScreenCaptureMode as Browser.
Viewing Current Execution on Sauce Lab's Dashboard
...
Open the associated execution profile.
Under Edit Additional Capabilities, 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.Download the Sauce Connect Proxy on any machine in the network using following url:
https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+ProxyExtract the folder at the suitable location.
You will find the sc.exe file in the bin folder.Open Command Prompt and navigate to the folder where sc.exe file exists.
Enter the following command.
Code Block sc -u <sauce_username> -k <accesskey> -i <tunnelID> For example: sc -u john.doe -k 8becc95c-4559-4582-a617-7d38544797a2 -i tunnel-1232
Press Enter.
...
For more information about executing test cases using W3C-Protocols and Capabilities, refer to the Sauce Labs documentation.
Execution on Sauce Labs Real Device-TestObject
Introduction
The Sauce Labs Real Device-TestObject provides you the ability to run Qualitia test cases across Android and iOS physical devices. With its Web interface, you can run tests using different combinations of platforms, platform versions, and browsers. In this environment all Qualitia mobile application tests are executed on physical devices. Sauce Labs allows you viewing video recordings of the test case executions.
To know more about Sauce Labs click here.
Prior starting offline execution on Sauce Labs, ensure you have;
...
Click App Upload > Choose File to upload the mobile application from your computer.
The application name appears.Mouseover the application name.
Click Settings.
Copy the File_id that is generated.
Form an app path in the format,as storage:File_id.
Enter the value of app_path in the first parameter for all the Mobile.OpenApp actions present in different test cases, which are planned for execution on TestObject.
Settings in the Associated Execution Profile:
You must create execution profiles that are solely used for execution on the Browserstack platform from the Qualitia Client. In those execution profiles, you must define the below settings that are mandatory for test suite execution.
...
URL
Username
Accesskey
Devicename
testobject_api_key
test_app_id
For testing on a native app, select nativeWebScreenshot as True.
For testing on an iOS application, select an Appium Version.
Additional Recommendations:
In the Execution Parameters tab, select ScreenCaptureMode as Browser.
Creating a Real Device Project
...
For more information about creating the project for Sauce Labs Real Device testing, refer to the Sauce Labs documentation.
| Info |
|---|
After logging to TestObject, click Data Center located at the top-right corner, and select the Time Zone to USE West 1. |
...
Log on to your Sauce Labs real device instance.
From the top, click
> Appium.
In the Appium Test Results section, click the test case from the list.
Here you can view the Test case Info, Screenshots, Video, Requests, Device Logs and Appium Logs.
...
To know more about Perfecto, click here.
Prerequisite:
An active user account on Perfecto.
...
From the Environment list, select as Cloud.
From the Cloud Platform list, select Perfecto.
Select the Edit Additional Capabilities checkbox.
Select or enter the following values:
Enter the following as URL
https://testingcloud.perfectomobile.com/nexperience/perfectomobile/wd/hubEither enter Username and Password, or SecurityToken.
Perform the following steps to execute the test suite on a mobile application,
Select enableAppiumBehavior as True.
To execute test suite on a mobile web application:
Select enableAppiumBehavior and useAppiumForWeb as Tru
Select AutomationName for Android as Appium and for iOS as XCUITest.
Enter SeleniumVersion to 4.0.0.
Enter the chrome driver version for the target mobile device, in ChromeDriverVersion to 2.xx, where xx denotes a chrome driver version, such as 91 and 92.
To execute test suite on an Android hybrid application:
Select enableAppiumBehavior and useAppiumForHybrid as True.
Enter SeleniumVersion to 4.0.0.
Enter the chrome driver version for the target mobile device, in ChromeDriverVersion to 2.xx, where xx denotes a chrome driver version, such as 91 and 92.
To execute test suite on an iOS hybrid application:
Select enableAppiumBehavior, useAppiumForHybrid,and iOSResign as True.
Additional Recommendations:
In the Execution Parameters tab, select ScreenCaptureMode as Browser.
| Note |
|---|
If you have used ID, Accessibility ID, and Class locator types when adding native mobile app objects in Qualitia, Perfercto Appium integration translates these all locator types to xPath at the time of test case execution. For more information, refer to the PerfectoMobile documentation. |
Viewing Execution Status and Reports in Perfecto's Execution Center
Once you have triggered the offline execution, you can view the status of your ongoing executions in Perfecto's Execution Center. Each test case appears on dashboard as a single grid with execution status against it. The status is updated after each test execution is completed in Perfecto's environment with its status (FAILED / SUCCESS) against it. Select the test case from the list and click Report from top to view recording of your test case.
| Info |
|---|
Qualitia and Perfecto's reports may mismatch if Qualitia test case contains any situation which ends the WebDriver session. This situation may arise due to the use of actions like Mobile.CloseApp, opening multiple WebDriver sessions in a single test case and so forth. |
To view the execution report of Qualitia test cases:
...
For more information on configuration of Perfecto connect, refer to the Perfecto documentation.
To configure perfecto to run test cases for the applications behind firewall:
Download Perfecto Connect executable depending on your OS.
Unzip the folder and run the file using command line interface along with Cloud URL and Security Token.
For example:Code Block perfectoconnect.exe -c <Perfecto_Cloud_URL> -s <Security_token>
Executing this file will give you the tunnel ID.
Under Edit Additional capabilities, enter the tunnel ID in tunnelId.
For more information about this, refer to the Perfecto documentation.
Limitations of Remote/Cloud Executions
...