TestLabRun
Last updated
Last updated
The Test Lab within Qyrus serves as a versatile and efficient platform for rapidly creating and executing test suites within a Project. It also facilitates the process of importing test scripts into these suites, thereby enabling the efficient execution of test scripts.
In this guide you will learn about:
A test suite is suite/collection of Test Scripts. Test Suites are a essential way of organising, maintaining test scenarios. They are different from modules as the suite can contain imported scripts from multiple modules. The main use of test suites, however is for batch execution, where each suite containing multiple scripts can be executed at once (script inside the suite are executed one by one in sequence in the same browser window)
Step 1: Navigate to the 'Web Testing', select the desired project, and click on 'Test Lab'.
Step 2: Click the 'New Test Suite' button.
Enter a 'Suite Name'.
Enter a 'Suite Description'.
Auto Add Test Scripts from Tags.
If you have test scripts that need to be added, check the 'Auto add test scripts from tags' option; otherwise, leave it unchecked.
These tags are utilized during script creation in the Test Repository.
With these tags, you have the capability to directly import scripts from the Test Repository to Test Lab while creating a Suite.
Note: If we create the suite without adding tags, only the suite will be created, and no scripts will be imported from the Test Repository, as depicted in the image below.
Click the 'Create New Suite' button.
Step 3: After creating the test suite and navigating to the Test Scripts page, you will be able to see Test Lab wiritten in the top-left corner. Additionally, on the far-left-hand side of the screen, you will find the count of test suites along with their respective names.
Step 4: If you intend to include the test suite within the Test Lab, you will observe a plus icon button on the far-left-hand side of the screen, adjacent to the test suite counts.
Click on this button and select the "Create New Test Suite" option for each additional test suite you wish to create.
1: Click on the three dots next to the suite name. You will see two options: "Edit" and "Delete."
2: To edit, click on the "Edit" option.
This will navigate you to the suite page where the suite name and description are prepopulated with the previous values. Click on the respective field to edit, and then click the "Update Suite" button.
After clicking, you will be redirected to the test script page, where you can see the updated suite name on the left-hand side panel.
3: To delete, click on the "Delete" option.
A prompt will appear to confirm the deletion. Click on "Delete Suite" to proceed. The suite will be deleted.
Previously created project.
Previously created test script.
Previously created test suite.
Step 1: Click the 'Import Test Script' button.
Upon navigating to the 'Import Scripts' page, there are a few things to note:
Displayed on the left half of the screen are previously created modules within the test repository.
On the right-hand side is the previously created test suite to which test scripts must be added.
To proceed,click on the desired module from the list on the left-hand side of the screen. This will allow you to select and import the specific test scripts associated with that module into the chosen test suite on the right-hand side.
Step 2: Utilize one of the following options to push the scripts to the suite:
Employ drag and drop functionality.
Use the blue 'Plus' icon located next to each test script.
Check the boxes on the left of the script names that you want to include individually.
If you want to import all the scripts present in the module, select the checkbox located in front of "Select All Test Scripts."
Step 3: After selecting your desired test scripts, click the 'Push to Suite' button to add them to the suite.
Step 4: Once you've made your selections, click the 'Save to Suite' button to finalize the addition of the chosen test scripts to the suite.
After navigating back to the 'Test Scripts' page, ensure that the desired test script has been successfully imported. You can verify this by checking the test scripts table located in the center of the screen. The imported script should appear within this table. Additionally, there will be a numerical indicator displayed on the 'Test Scripts' heading, indicating the total number of test scripts present. This indicator helps confirm the successful import of the desired test script.
Step 5: If you wish to import the test script into the suite once more, you need to follow these steps:
Click on the "Import Scripts" button.
This action will take you to the import scripts page where you can choose the test scripts you want to include in the suite.
Follow the same procedure as before to select and push the desired test scripts into the suite.
After making your selections, remember to click the 'Save to Suite' button to finalize the import of the chosen test scripts.
Previously created project.
Previously created test script.
Previously created sprint.
Previously created test suite.
Step 1: You will notice a plus icon button on the far-left-hand side of the screen, next to the test suite counts.
Click on this button and select the option to import from a sprint. This action will take you to the sprints page, where you will find two import options: "Import from Active Sprint" and "Import from Other Sprint" (which is not currently active or started).
Choose the sprint you desire, from which you want to select the suite for importing into the current sprint.
Step 2: After clicking the desire sprint you will see a option to import suite after select the checkbox for the suite you want to import and then click on import to test suites
Step 3: Once the suite is imported, you will be redirected to the test script page. On the left-hand side of the screen, you will observe the suite count getting updated to reflect the newly imported suite. In the center of the screen, you will be able to view the scripts that are present within the imported suite.
Previously created project
Previously created test script
Previously created test suite
Test script previously imported
Step 1: Navigate to the web testing platform and choose the desired project.
Once in the project area, locate and click on the "Test Lab" section.
Now, choose the test suite from which you intend to execute test scripts. This selection empowers you to effectively manage and carry out tests specifically from the chosen suite.
Step 2: To execute the test script, you have two options. Choose one of the following methods:
1. Select the checkbox in front of the script name to choose the script you want to execute. Alternatively, if you wish to select all the scripts, you can use the checkbox located next to the total script count. This will enable the execution of all the selected scripts.
As a result, the previously disabled execute button will become enabled.
Click the execute button. Upon doing so, you will be presented with two options: Dry Run and Execute Test . After selecting either of these options, you will be directed to the execution page where the chosen scripts will undergo the specified type of execution.
2. Click on the arrow button located next to the total step count in the script. This action will navigate you to the Test Steps page.
On this page, you can view all the steps that are present within that specific script.
If you want to edit the script, click on the edit step icon located at the top right corner. Once you click the icon, it will switch to edit mode, which you can toggle back to view mode.
Once you've made your edits, you can save the script using the save button.
Click on the execute button. Once you click it, you will be presented with three options: "Dry Run", "Execute Test", and "Performance". By selecting one of these options, you will be redirected to the execution page.
Step 3: You can click the below link for the run types to continue the execution steps
Step 1: Navigate to the web testing platform and choose the desired project.
Once in the project area, locate and click on the "Test Lab" section.
Once you click on "Test Lab", you will be directed to the test script page. From here, you can initiate the execution of test suites.
Step 2: Select the checkbox in front of the suite name to choose the suite you want to execute. Alternatively, if you wish to select all the suites, you can use the checkbox located next to the total suite count. This will enable the execution of all the selected suites.
As a result, the previously disabled execute button will become enabled.
Click the execute button. Upon doing so, you will be presented with two options: Dry Run and Execute Test . After selecting either of these options, you will be directed to the execution page where the chosen suites will undergo the specified type of execution.
A dry run refers to the process of executing a script or a suite with basic functionalities before performing a full-scale operation.
1: On the left side of the screen, there is a panel where you will find the option to "Run with Configuration." This feature can be utilized if you have configured the run settings during the project setup phase.
If you have completed the run configuration setup, you can toggle this option to enable it. However, if you haven't configured the run settings previously, you will need to make selections for various execution parameters Browser Selection, Database Query, Notify Me, Environment Variable,
2: When selecting the browser, you'll encounter two options in the center of the execution page: "Dedicated" or "Shared Pool." You should select one of these options to specify the browser in which the execution will take place.
Note: Next to the "Shared Pool" option, you will find a local Run option. To gain a better understanding of the Local Run feature and its utilization in Qyrus, Kindly refer to the Encapsulate documentation for more information.
3: The second option is "Database Query." If you've set up the database query configuration during the project setup, clicking on the database query will present you with the choice to select a database. If you haven't configured this setup, you can skip this step.
4: The third option is "Notify Me." If you need to share the test result with others, you can enter their email addresses here. This step enables you to notify them about the outcome of the execution.
5: The fourth option is "Verify OTP." If your test script includes the feature to verify One-Time Passwords (OTPs), you can enable this option. Otherwise, you can skip it.
6: After selecting the options, you can verify them in the summary section, where you'll find the following details:
Execution Parameter File: This parameter allows you to enable or disable it, based on the parameterization you have implemented in the script.
Choose Environment Variable: This option lets you select the environment variable that you previously created during the project setup phase.
Choose Screen Resolution: This allow you to specify the screen size on which you want the execution to occur.
Executing: This section displays the total count of scripts.
Selected Browsers: Here, you can view the browsers you have chosen for execution.
Database Name and Type: This information is visible if you have made a selection related to the database setup.
7: After verifying the summary section, click on the "Run Test" button located at the top right corner. Once clicked, you will be directed to the test steps page, where you can monitor the status of the execution.
8: Once the execution is completed, you will notice an arrow button. Upon clicking this button, you will be navigated to the reports page.
The Reports page provides comprehensive information about the execution results, including details about passed and failed script steps, logs,screenshots and more relevant data. For further understanding of the reports section in Qyrus, kindly click on the provided link Reports .
Executing a test involves running a script or a suite to assess its behavior and performance. It specifically entails running a script with advanced features and functionalities.
1: On the left side of the screen, there is a panel where you will find the option to "Run with Configuration." This feature can be utilized if you have configured the run settings during the project setup phase.
If you have completed the run configuration setup, you can toggle this option to enable it. However, if you haven't configured the run settings previously, you will need to make selections for various execution parameters Browser Selection, Database Query, Notify Me, Environment Variable, Screen Resolution and Healer AI
2: When selecting the browser, you'll encounter two options in the center of the execution page: "Dedicated" or "Shared Pool." You should select one of these options to specify the browser in which the execution will take place.
Note: Next to the "Shared Pool" option, you will find a local Run option. To gain a better understanding of the Local Run feature and its utilization in Qyrus, Kindly refer to the Encapsulate documentation for more information.
3: The second option is "Visual Testing." Visual testing in Qyrus helps you test the appearance and user experience of your applications by validating layout and content. To learn how to use visual testing in Qyrus, please click on the link Visual Testing .
4: The Third option is "Schedule Test." Scheduling a test in Qyrus allows you to specify the exact date, time, and region for executing the chosen script or suite.
There are two options available in Qyrus for scheduling tests, allowing you to tailor test executions according to your specific testing needs. These options are "Schedule Once" and "Schedule Repeat."
Schedule Once: In this option, you are required to select a specific date, time, and timezone. As per the provided details, the test will be executed once, precisely on the chosen date, time, and timezone.
Schedule Repeat: Under the "Schedule Repeat" option, there are three sub-options to consider:
Schedule Weekly: To utilize this choice, you must select a day of the week, date, time, and timezone. The test execution will follow the specified details, adhering to the designated weekly schedule.
Schedule Daily: This option necessitates the specification of an end date, time, and timezone. The test will be executed daily until the defined end date, observing the designated time and timezone.
Schedule Hourly: To employ this option, you need to select a particular date, end time, and timezone. The test will be scheduled on the chosen date and will be executed repeatedly until the specified end time, while considering the selected timezone.
5: The fourth option is "Database Query." If you've set up the database query configuration during the project setup, clicking on the database query will present you with the choice to select a database. If you haven't configured this setup, you can skip this step.
6: The fifith option is "Notify Me." If you need to share the test result with others, you can enter their email addresses here. This step enables you to notify them about the outcome of the execution.
7: The sixth option is "Healer AI." Healer AI operates by intelligently adapting locators for elements that have undergone changes in your tests, resulting in enhanced test reliability and stability. To learn how to use Healer AI in Qyrus, please click on the link Healer AI .
8: The seventh option is "Verify OTP." If your test script includes the feature to verify One-Time Passwords (OTPs), you can enable this option. Otherwise, you can skip it.
9: After selecting the options, you can verify them in the summary section, where you'll find the following details:
Execution Parameter File: This parameter allows you to enable or disable it, based on the parameterization you have implemented in the script.
Choose Environment Variable: This option lets you select the environment variable that you previously created during the project setup phase.
Choose Screen Resolution: This allow you to specify the screen size on which you want the execution to occur.
Executing: This section displays the total count of scripts.
Selected Browsers: Here, you can view the browsers you have chosen for execution.
Executing with Healer: This information is visible only when you have chosen the option to execute using Healer AI
Executing with Visual Testing: This information becomes visible if you have chosen the visual testing option for executing the test with visual testing.
Scheduled: The option to schedule becomes visible when you have selected the "Schedule Test" option. It displays the scheduled date and time information.
10: After confirming the details in the summary section, click on the "Run Test" button situated at the top right corner. It's important to note that if you have chosen the "Schedule Test" option, the "Run Test" button will transform into a "Schedule Test" button accordingly. Upon clicking the button, a pop-up screen will emerge, offering you two choices:
Go Back: This option allows you to return to the test steps page.
Go to Reports: Opting for this alternative guides you to the reports section. Within the reports, you can access and evaluate the ongoing execution's status in a comprehensive manner. For further understanding of the reports section in Qyrus, kindly click on the provided link Reports .
Performance testing involves evaluating the behavior and responsiveness of a system under a specific load, which can include simulating a certain number of users interacting with the system.
In Qyrus you would execute a test script while simulating a defined number of users to observe how the system performs under such conditions.
Step 1. When you navigate to the execution page, on the left-hand side of the panel, you'll encounter two options. The first option is "Performance Load."
When you select this option, in the center of the page, you'll find an input field where you can specify the number of users you want to simulate during the execution of the test script.
This allows you to gauge the system's performance under different user loads.
Step 2. There is also an option to schedule a test, although it is entirely optional. When choosing this option, you need to select the checkbox and specify a particular date, time, and timezone. Based on the information provided, the test will be executed as a one-time event, specifically at the selected date, time, and timezone.
Step 3. The second option is "Database Query." If you've configured the database query settings during the project setup phase, clicking on this option will allow you to select a specific database. If you haven't set up this configuration, you can skip this step.
Step 4. After selecting the options, you can verify them in the summary section, where you'll find the following details:
Execution Parameter File: This parameter allows you to enable or disable it, based on the parameterization you have implemented in the script.
Choose Environment Variable: This option lets you select the environment variable that you previously created during the project setup phase.
Executing: This section displays the total count of scripts.
Database Name and Type: This information is visible if you have made a selection related to the database setup.
Step 5. After verifying the summary section, click on the "Run Test" button located at the top right corner. Once you click, a pop-up screen will appear, presenting you with two options:
Go Back: This option will navigate you back to the test steps page.
Go to Reports: Choosing this option will direct you to the reports section. In the reports, you will be able to view and assess the current status of the execution, providing you with detailed information about the outcome. For further understanding of the reports section in Qyrus, kindly click on the provided link Reports .
