TABLE OF CONTENTS
2. How to Execute Scripts in algoQA from Test Scripts Page
3. How to Execute Scripts in algoQA from Script Generation Pop-up
1. Overview
This article provides detailed information on the process to be followed for executing scripts in algoQA. You can execute scripts directly from the Test Scripts page or Script Generation pop-up. Scripts can run in Headless or GUI mode, with options to upload reports, use custom tags, enable auto-healing, or run in debug mode. Execution progress and results can be monitored on the Script Execution page, and detailed summaries and logs are available after completion.
Note: This feature is currently available only for Java selenium framework.
2. How to Execute Scripts in algoQA from Test Scripts Page
- Once the script has been generated, a play icon button will be available next to the script on the Test Scripts page. Click the icon to execute the script.

- The Script Execution Process pop-up window will appear.

- Choose whether you want to execute the script in Headless mode or GUI mode. In Headless mode, only the command prompt is visible, and the execution UI is not displayed.
- When GUI mode is selected, both the command prompt and the execution UI are visible during execution.
If you want to upload the execution report to the dashboard, select the I agree to upload the script execution report automatically to the dashboard checkbox and enter the batch name and test suite name in the respective fields.
- If you want to execute the script with a custom tag, select the “Do you want to execute with custom tag” checkbox.
- A command is available to execute scripts using custom tags. For example, if the @test001 tag is used, only the first test case in the script will be executed. By entering a specific custom tag, only the test cases associated with that tag will run.
- Format for entering custom tags:
Single tag: @test001
Multiple tags: @test001 or @test002 - If automatic autohealing is required during execution, enable the Do you want to autoheal the script during execution checkbox.
- If you wish for the execution UI to remain active post-execution, check the Run container in debug mode; it will remain active until explicitly terminated checkbox.
- After selecting the required fields, click Proceed.
- The Script Execution page will appear, where you can also view the execution pipeline. From this page, you can see all previously executed scripts.

- A green tick mark indicates that the script has been executed. Click on it to view the status log.

- On the Script Execution page, a Filter option is available next to the search field. You can:
Filter by date: Today, Last Week, or Custom.
Filter by user: select a name from the Executed By dropdown.
Filter by status: choose from Completed, Failed, Terminated, Queued, or Running.
After selecting the desired filters, click Apply to view the results.
- If you had choose GUI mode then you can view the execution preview with command prompt and you can also view them in full screen and minimize back if you don't want to see in full screen.

- When Headless mode is chosen, the execution runs in the command prompt without displaying the execution UI.
- After the script execution is complete, select the script to access the Execution Summary, Tests Summary, and Pipeline Summary details.

- The Execution Summary section displays key information about the script execution, including Execution Mode, Status, Start At, End At, Executed By, Batch, Test Suite, and Tag.
- The Tests Summary section provides an overview of the test results, including Total Tests, Passed, Failed, Skipped tests, and the Duration of execution.
- You can download the execution report by clicking Download and view the execution log by clicking Execution Log.
3. How to Execute Scripts in algoQA from Script Generation Pop-up
- In the Test Case Generation pop-up, after the test cases are generated, click Generate Script.

- The Script Generation pop-up will appear. Once the script is generated, click the Execution button.

- Follow step no 2 to 18 from previous section
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article