...
Familiarity with the application you're testing.
Access to Qualitia Automation Studio - Client.
Basic understanding of test cases.
Availability of existing test cases.
Privileges to execute Teststests.
➕ Create a Test Suite
You are introducing a new module in your application. To ensure it integrates well, you decide to create a new test suite for it.
...
Info |
---|
You can also perform the following actions: Move Line Up: Click Move Line Up to shift the test case one line up. Move Line Down: Click Move Line Down to shift the test case one line down. You can change sequence of test cases in a suite by using the Move Line Up and Move Line Down options from the top menu bar. Flag: You can apply flags for each test case or a global flag to mark multiple test cases. You can select from the options Continue, Exit Test Case, or Exit Suite. If a test case fails, the execution can either Continue, Exit Test Case Iteration, or stop by exiting of the entire suite. Export: This option allows you to export the execution files. Hover over Export Execution File and you will see two options: Export Execution Files: Select Export Execution Files if you want to export the direct files. Export the published test cases: Select Export the published test cases if you want to export the published test cases.
Refresh: If multiple users are working on the Suite, and one of the users update the suite you will see a Red Dot near the Refresh button. The Red dot indicates update in the suite. Click Refresh if you want to incorporate the changes; else continue.
You can view the published test case details, such as the published date-time and the username, under the Published Status column on the Suite screen. Hover over the in the Published Status column to view the details. On the Suite Explorer screen, when you click on the parent Suite you will see two tabs. Suites: Clicking Suites will show the list of existing suites under the selected project. It will display the Suite Name, Description, Updated On, and Updated By details. You can also Edit, Delete, and Schedule a new schedular from the top menu bar. Schedules: On this screen, you can view the list of schedules available for the project. It will display details such as Scheduler Name, Test Suites, Scheduler with Run, Frequency, Created On, and Created By.
|
Execute from Selected Step
QAS allows you to execute a test case starting from any step you select. Simply choose the desired step and click Execute from Steps to run the test from that point onwards.
This feature is only available for Desktop projects.
To execute from selected step:
Select the step.
Right-click on the step to open the contextual menu.
Select Execute from Steps.
Info |
---|
If you select multiple continuous steps, the selected steps and all subsequent steps will execute. If you select multiple discontinuous steps, execution will start from the last selected step. If you select all steps in the test case, the entire test case will execute. The Execute from Steps option is available on task header also. If execution is started from the task header, the task's steps and all test case steps following the task will execute. If you select a step within a task, the execution will begin from that step, and all steps within the task and subsequent test case steps will execute. The Execute from Steps option is not available for skipped steps or notes. For conditional statements, the Execute from Steps option is only available for the if condition. It is not available for else if, else, or any conditional steps. If iterations are set, all iterations will execute.
|
👁️ View Test Suite Execution Report
After executing the test suite, you want an overview of the results to identify any issues or areas of improvement.
If RealTime Real Time Reporting is enabled, view the report directly in the Real Time Reporting portal.
Every test suite execution also saves a summary report at a specified location.
If not on Real Time reportingReporting, you can upload the local report.
...
The Scheduler execution is not working on Safari browser due to a failure of Webdriver object creation.
...