Execution
Executing
Test Execution
There are two ways of executing your tests with Qyrus
Suite Execution
Script Execution
Suite Execution
A suite execution will perform an execution on every script inside of the selected suite. Qyrus also allows the user to execute multiple suites at once. To run a single suite or multiple test suites, the user must first navigate into a project, check the suites to execute, click on the Execute button, and finally, select Execute Run.
Script Execution
The user has the option to perform a single script execution or multiple script executions at once.
Single Script Execution
To run a single script execution, the user must first go into a project, navigate into a test script, click on the Execute button, and finally, select Execute Run
Multiple Script Executions
To execute multiple scripts, the user must first navigate into a project, check the scripts to execute, click on the Execute button, and finally, select Execute Run.
Dry Run
Executing a test as a dry run will display pass/failed results but the results do not appear in the overall test reports. Dry run executions can be done with both suites and scripts.
Suite Dry Run
A suite dry run will perform a dry run on every script inside of the selected suite. Qyrus also allows the user to perform a dry run multiple suites at once. To perform a dry run on a single or multiple test suites, the user must first navigate into a project, check the suites to perform a dry run, click on the Execute button, and finally, select Dry Run.
Script Dry Run
The user has the option to perform a single script dry run or multiple script dry runs.
Single Script Dry Run
To perform a single script dry run, the user must first go into a project, navigate into a test script, click on the Execute button, and finally, select Dry Run
Multiple Script Dry Run
To execute multiple script dry runs, the user must first navigate into a project, check the scripts to execute, click on the Execute button, and finally, select Dry Run.
Required Fields
After clicking on the ‘Execute’ button and either selecting Execute Run or Dry Run, the user will be navigated to a similar page like below.
Note: When selecting Dry Run, the advanced options will not appear
The required fields in this form are the following:
Selecting the application
Selecting the device
Selecting your application
When selecting your application for execution, the user has two different options
Install App
Launch App
Install App
If the app is not already installed on the device, the user must select this option to continue with their execution. To execute your test via the Install App, click on the dropdown and choose an IPA or APK file. If there is no file available, please navigate into Setup → Application Management and upload an IPA or APK file.
Launch App
Launch app can only be used if the application is already installed on the device. If the application is installed on the device, the user must select the Launch App toggle and enter the correct app activity and app package into the input fields
Selecting your device
Note: When selecting your device for execution, no other user must be using the device at that time. If another user is connected to that device, your test will be put in a queue and not begin execution until that device is no longer being used by another user.
The user has two different options when selecting an execution device.
Selecting a single device
Selecting a device pool
Single device
When the user clicks on the Select Device dropdown, every device configured to the user’s account will appear as a selectable option for execution.
Device pool
Selecting the Use device pool checkbox will change the items in the dropdown list from single devices to all of the user’s created device pools. After selecting a device pool, the execution will run on every device in that pool. If the user has no device pools but wishes to set one up, please navigate to Setup → Device Pool and then select the New Device Pool button.
Execution strategy
The user has 2 options as to how they want to allocate their devices for execution:
First Available
Device Coverage (Default)
This selection will determine how many executions are triggered as denoted by the total test reports generated section.
First Available
Each test will be executed once. Priority is given to selected device(s) with the least number of tests in their queue. Using this strategy without a device pool, the first available device the user has access to will be chosen to execute each test. If a device pool is selected, the first available device in the pool will be used to run each test.
Device Coverage
Each test will execute on all selected device(s). Using this strategy without a device pool, each test will be executed on the selected device. If a device pool is selected, each test will be executed on all of the devices in the pool. Therefore, the number of executions triggered would be equal to number of tests selected * number of devices selected.
Optional Fields
The following fields are all optional to run an execution
Reset App
Togging Reset App will reset the app storage and cache of the application
Healer
Healer is an AI tool that is used to help find a new locator for a failed step in a test execution. Healer does require a passing baseline to find a new locator for the failed test step.
OTP
If the user’s test script is using the action type Verify Otp, toggle this value to active.
Email
If the user needs to send an email of test execution reports, toggle this to active and enter an email into the respective input field.
Advanced Options
Note: If performing a dry run, the advanced options will not appear
Click on the plus icon next to Advanced Options and two more tabs will appear with the following options:
Schedule Execution
Database Configuration
Schedule Execution
After toggling on Schedule Execution, the user will have options to do the following:
Schedule Once
Schedule on repeat
Schedule Once
To schedule a test once, the following is required
Start date
Time zone
Time
Schedule Repeat
Scheduling a repeating test can be done weekly, daily, or hourly
Weekly
The required fields for scheduling a weekly execution are the following:
Days
Time
Time zone
End date
Daily
The required fields for scheduling a daily execution are the following:
Time
Time zone
End date
Hourly
The required fields for scheduling an hourly execution are the following:
End time
Time zone
End date
Note: Failed scheduled tests will be retried automatically once.
Database Configuration
When using the Execute Query action type, the user must select a database from the dropdown. More information regarding database configuration setup can be found here.
Last updated