Questions about supported languages, frameworks, and how algoQA generates and customizes scripts. Select a question to expand its answer. C#, Python, Java, JavaScript, and TypeScript. You can update object IDs in the following ways: - algoScraper: Scrape all the UI elements and update Object IDs. - Re-scrape: Re-scrape capability reevaluates the application under test to identify and locate objects. - Auto-healing: A proactive approach to handle changes in object IDs or locators, ensuring that the changes can adapt to application changes. For detailed information, see the [Auto Healing](/build-and-automate/using-the-platform-for-automation/executing-the-tests/auto-healing) article. - Edit Object Repository in the algoQA Feature: Access and modify object IDs in the Object Repository file within the Profiler feature. Changes made here apply to all relevant scripts. - Within Scripts: Alternatively, you can update object IDs directly within scripts. Note that these changes are specific to the script. algoQA covers the automation of various applications and types of testing, including: - Application: Web, Desktop, Mobile, and Hybrid. - Types of testing: Smoke Testing, Regression Testing, Release Testing, User Acceptance Testing, Performance Testing, Security Testing, and Load Testing. For API automation, algoQA supports tools like Selenium, Protractor, Playwright, Cypress, Karate, Appium, Squish, Sikulix, FlaUI, WinAppDriver, TestComplete, and LeanFT, as well as RestSharp and RestAssured for Java and C# scripting, respectively. It also supports execution engines such as JBehave, NUnit, JUnit, TestNG, Cucumber, SpecFlow, and Pytest. Yes, algoQA supports fetching all properties of a control including coordinates during execution. You can print this information in the report as well. The scraper for Qt applications is currently under development and will be available from July 2026. Yes, all objects are exported to a script file for viewing and editing. algoQA supports intelligent image comparison as well as image recognition. The image comparison tolerance can be configured based on your requirements. Yes, coordinate-based (direct or from XPath/locator) or image-based actions are supported. Default actions include drag-and-drop, right-click, double-click, and similar interactions. For actions not covered by default (such as long drag), custom actions can be implemented using Code Bot. Using custom actions, the driver created per app can be used to switch context for pop-ups or other apps. algoQA integrates with Robot Framework to handle OS-level pop-ups. The scraper maintains an object cache only for a specific instance or run, and all object information is stored and managed in the algoQA offline model. It also has the ability to use unique properties to handle dynamic controls. For web applications, automated scraping can be performed using an AI agent for each screen, whereas for desktop applications, scraping needs to be done screen by screen. algoQA functions differently than traditional record and playback tools for application testing. algoQA uses an offline model of the application under test (AUT) for automation, whereas record and playback tools rely on recording user interactions to generate test scripts. algoQA does not require any code to be written for the application under test before starting the automation process. Instead, you can begin with inputs like Wireframes and Swagger documents. Test Design the application is the only manual effort required, which is easy to understand. In contrast, record and playback tools may require significant manual effort to maintain test scripts as the application undergoes changes. Additionally, algoQA supports end-to-end testing, handling UI, API, and database interactions within a single test case. Yes, algoQA generates scripts in the preferred technology of the user. algoQA allows you to reuse existing automated test scenarios or scripts by integrating them into the platform. This can be achieved through the following methods: 1. Manual Import: You can manually import your existing test scripts into algoQA using the "Import Test Script" feature. This method is suitable for smaller projects or for users who prefer a more manual approach. 2. Automated Import: For larger projects or for users who prefer an automated approach, you can use the "Record Scenario" feature to record new test scenarios using your existing scripts as a base. This method allows algoQA to learn from your existing scripts and generate new test cases based on the recorded actions. 3. Script Extension: If your existing test scripts are written in a supported language, you can extend their functionality by adding custom code or plugins in algoQA. This method allows you to leverage the power of algoQA while maintaining the functionality of your existing scripts. 4. Script Reuse: Once your test scripts are imported or extended, you can reuse them in multiple test cases or test runs. This helps to save time and effort while maintaining consistency across your test suite. algoQA does not directly migrate scripts from one framework technology to another. However, you can manually convert and adapt the scripts to the new framework technology. The structured folder format of algoQA-generated scripts makes it easier to locate and manage the scripts during the conversion process. algoQA helps maintain automation over time by allowing you to automate the process of automation. This means that you can scale your existing test automation solution significantly and reduce costs. Additionally, algoQA follows an open architecture, making it possible to extend your existing platform with its features. If you encounter any issues or need assistance, AlgoShack offers consulting and professional services to help optimize your product. Yes, algoQA allows you to align newly generated test cases with an existing automation framework. You can import your existing test scripts and files into algoQA, preserving your prior work. Additionally, you can organize your test scripts and resources within your framework as needed, making it easy to integrate new test cases with your existing automation efforts. Yes, algoQA handles windows alerts and file upload/download popups. The framework includes various utilities to verify the content including database data, PDF, and Excel files. Tests in algoQA can handle conditional flows or loops by using the Record Scenario feature to record the workflows for different dynamic values. This allows generating separate Feature Files for each condition or loop iteration. For example, you can record the workflow for a Home Loan and generate a Feature File, then record the workflow for a Car Loan and generate another Feature File. This approach ensures accurate testing of all possible conditions or loop iterations. You can inject your own code into the algoQA framework to test dynamic workflows, and algoQA Codebot can be used to create these custom functions. Yes, custom actions can take parameters for reusable flexible logic. You can configure custom actions to accept parameters. You can use algoQA Codebot and the custom settings editor to provide reusable parameters. Yes, you can modify or add node modules by using the customize framework feature. You can use code from other languages, but it should be compatible with the existing language and framework. No. Any changes made in the downloaded script do not reflect in algoQA. You must update the changes in algoQA to reflect new changes in the script. You can upload custom files if there are any changes made. algoQA functions based on the offline model of an application under test (AUT). algoQA does not perform any Record and Play on any application under test. You can start with the process of automation using algoQA even when a single line of code is not written for the application under test. You can begin the process of automation with the same inputs as the ones that go into the development streams, such as Wireframes and Swagger documents. - For Web and Mobile automation: You can use the algoScraper tool, which is a Chrome extension. This tool is used to fetch all the available UI elements and XPaths in a web page. - For Desktop automation: You can choose a desktop automation tool or framework, such as TestComplete or Squish, that is designed to scrape the UI elements. You can either make test design changes or edit the scenarios to regenerate test cases and test scripts. - algoQA scripts generated follow an organized folder structure including configuration files that allow you to modify the application URL. - You can update the application URL by making the changes in the Application Settings file. - You can also modify the application URL in the Project Settings page, which displays various configuration and preference settings related to a specific project or application. To access the Project Settings page, navigate to Settings > Project Settings. With the algoQA platform, you can automate the process of automation, scale it significantly, and reduce the cost, all at the same time. It is possible to extend your existing platform with algoQA, provided your existing platform follows open architecture. Protecting your existing test automation investments with algoQA: - Seamless Integration: algoQA fits seamlessly into your test automation ecosystem without disrupting anything you currently use. - Accelerate automation: The purpose of algoQA is to accelerate automation, protecting your existing investments in tools and frameworks. All your current investments in tools and frameworks will remain intact. - Framework Extension: Even if you already have an automation framework, algoQA can extend its capabilities, provided your framework follows an open architecture. - Script reuse: You can reuse your current test scripts. algoQA is extensible. - Custom Actions functionality: The algoQA platform allows you to create custom actions to incorporate your application-specific testing requirements. - Configuration functionality: The algoQA Framework can be configured to suit your requirements as given below: - Upload existing Files: You can upload your existing test scripts and files into algoQA, preserving your prior work. - Create new Files: Generate new test scripts and files tailored to your specific requirements. - Organize files and folders: Arrange and structure your test scripts and resources within your framework as needed. By utilizing these capabilities, you can fully customize and extend your framework to match your testing needs while safeguarding your existing automation investments. Coordinate-Based Testing is an approach used in automated testing when applications do not expose traditional "locators" or automation IDs. This applies in situations where testability considerations are not incorporated into the application's architecture, particularly in legacy or green screen applications. algoQA integrates with tools like Sikuli, Squish, and TestComplete, supporting Coordinate-Based Testing and allowing you to perform testing in scenarios where traditional locators are not available or applicable. In coordinate-based testing, automation tools rely on techniques such as Optical Character Recognition (OCR) or image comparisons instead of using traditional "locators" to identify and interact with elements on the screen. algoQA handles locator issues with shadow DOM or iframe elements by integrating with tools like Selenium, Sikuli, and TestComplete, which support Coordinate-Based Testing. This approach relies on techniques such as Optical Character Recognition (OCR) or image comparisons instead of using traditional locators to identify and interact with elements within shadow DOM or iframes. algoQA automatically generates automation scripts, and these scripts are fully accessible to users. You can: - View and edit the generated scripts - Download the scripts for local use - Execute them independently outside the platform This is where algoQA fundamentally outperforms Postman. algoQA automatically generates BDD feature files and scripts, eliminating the need for manual conversion using the algoQA offline model, but not from Squish recordings. When using Squish with algoQA, the process involves the following steps: 1. Recording Scenarios: Use the Record Scenario feature to record the workflow or scenario. The recorded scenario is saved in the sequence it was recorded. 2. Generating Test Cases: Generate Test Cases after recording a scenario. 3. Analyze and Generate Scripts: In the Test case generation pop-up window, click "Generate Script." Ensure you select the appropriate language, framework, and Report Type by clicking the settings icon. Scripts will be generated and can be downloaded to your desired location. 4. Execution: You can execute the generated scripts either by opening the Feature File in Squish and running the scenarios or steps, or by using the command prompt to provide command-line instructions. This streamlined process ensures that test cases and scripts are automatically generated from recordings, reducing the need for manual intervention. Yes, you can modify only specific screens instead of re-recording the entire scenario. The offline model created for test design is editable. It can be extended or modified based on application changes, and scenarios can be recorded. Also, existing scenarios can be edited to include changes in the offline model. Changes to recorded scripts can be made quickly by following these steps: 1. algoQA Access: Open the algoQA where the recorded scripts are stored. 2. Modify Steps: Update the necessary steps within the scenario. algoQA is designed for reusability, so changes in one script can often be reflected across others using the same step definitions. 3. Save Changes: After making the required modifications, save the changes. 4. Re-execute: Once saved, the updated script can be re-executed to verify the changes. Ensure that the environment settings (like WebDriver path and browser type) are correctly configured if you are switching between different execution environments (e.g., from Chrome to Edge). If changes are made outside of algoQA, they need to be manually updated in the offline model of the Application Under Test (AUT). Yes, scripts can be regenerated anytime. Yes, existing scripts can be reused across releases. algoQA is designed to allow easy updating and maintenance of test scripts, ensuring they can be adapted to new testing requirements. Yes, multiple scenarios can be handled within the same script in algoQA. Prerequisites for Running TypeScript Playwright Scripts: 1. Install Node.js and NPM: Download and install the latest version of Node.js from the official website. 2. Install Playwright: Once Node.js and npm are installed, open Command Prompt (CMD) and run `npx playwright install`. This command installs Playwright along with the required browsers. 3. Install Allure Commandline (for report generation): To generate Allure reports, install the Allure command-line tool globally with `npm install -g allure-commandline`. 4. Running the Tests: After your test script is created: - Install dependencies (only once per project/script): `npm install` - Execute the test script (every time you run it): `npm run test` Yes, algoQA comes with a user-friendly UI for configuring API details. Endpoints can be configured in the UI based on the requirement. algoQA can generate scripts in Java Selenium format for integration with your existing TestNG framework. This feature reduces rework by using auto-healing scripts, minimizing maintenance caused by frequent UI changes. Yes, feature files from Ruby can be used to auto-generate efficient Python scripts with optimized approaches, rather than just direct code translation. Yes, existing automation artifacts like feature files and scripts can be imported, translated to new languages (e.g., from Ruby to Python), and optimized without rewriting from scratch. Scripts authored in one framework (like Selenium) can pass execution and data to other automation tools (Tosca, SmartBear), supporting distributed testing across a diverse solution landscape. Migration is achieved by converting BDD feature files rather than scripts, provided both platforms are supported. Yes. Using the original feature files, algoQA can generate new and more efficient Python scripts, optimizing language differences rather than direct line-by-line conversion. algoQA uses AI and auto-healing for changes in the application (locators, labels, etc.), minimizing manual script maintenance and optimizing existing scripts for new environments. algoQA supports functional clicks on image elements. A test script can be created to locate and interact with image-based UI items, with logs or script outputs available for review. Image clicks are handled similar to other element types, provided the image was scraped. To handle shadow DOM or iframe elements or missing locators in algoQA, you can use the XPath Mapping functionality. Here is how: - Shadow DOM or Iframe Elements: If you encounter shadow DOM or iframe elements, you can update the XPath expressions to target the specific elements. In the XPath Mapping screen, upload the scraped file containing the new XPath expressions for the shadow DOM or iframe elements. Then, select the matching UI element or elements and click the "Remove" button to replace the old locators with the new ones. - Missing Locators: If a locator is missing, you can re-scrape the UI elements using the Scraper Tool Window. After scraping, search for the missing UI element using the search functionality. Ensure that your search criteria are accurate and relevant to the data you are trying to retrieve. If you use invalid values in the search bar, you will see an error message. Once you find the missing UI element, update its XPath expression using the XPath Mapping feature. Remember, the XPath mapping feature is specific to the UI elements' name, type, and XPath expression. For example, when multiple controls share the same UI element name but different XPaths or UI element types, and if you map an XPath to one of these UI elements in the XPath Mapping feature, the XPath will be updated for that particular UI element with its specific UI element type and XPath. The XPaths of other UI elements with the same name but different XPath expressions or UI element types remain unchanged. algoQA generates scripts in the preferred technology of the user and organizes them in a structured folder format for easy management. These scripts can be downloaded and executed locally on a machine or on virtual machines. The flexibility of the scripts allows for easy integration into the user's environment. Additionally, scripts can be scheduled for later execution and run either sequentially or in parallel, providing versatile options for script execution. You can use a common XPath expression while scraping elements. For more information on scraping common XPaths, refer to the [algoScraper as an extension](/automation-by-application/web-application-test-automation/scraping-user-interface-elements/algoscraper-as-an-extension-for-web-applications) article and update the locators using the XPath Mapping feature. For more information, see the XPath Mapping article. You can migrate algoQA-generated scripts to your Integrated Development Environment (IDE). The scripts are organized in a structured folder format, making them easy to navigate once imported into your IDE. For example, to view and work with Java Selenium scripts generated by algoQA in your IDE, ensure that the necessary configuration steps are completed. You can then download and import the scripts as a Maven project, which allows you to manage the scripts within your IDE. Code generation cannot be performed directly within the IDE. However, you can analyze the failures in the scripts. algoQA generates scripts in the automation framework of your choice like Selenium, Appium, etc. If there are new test cases added to the test suite, scripts can be generated with those added test cases. Yes, algoQA extends the standard actions with options to create custom actions wherever required. It depends on what can actually be exported out of Ranorex. Where a tool allows scripts or test cases to be exported, algoQA has been used for similar porting before — for example, converting Selenium scripts to Playwright, or Protractor scripts to Playwright, or even manually written test files/URD to test scripts. The team would need to see what Ranorex's output looks like to confirm whether it can be converted into the target framework. This varies by tool. Some tools are fully closed, so nothing meaningful can be extracted. The team would need to check specifically what Ranorex permits before confirming a migration path. If the custom test hooks expose callable functions and parameters — even without full access to the underlying product code — they can be leveraged within the test automation framework. The associated DLLs or supporting libraries can be imported as custom utilities and reused by algoQA-generated scripts, eliminating the need to reimplement existing functionality. For example, in an ultrasound application with a custom virtual touch panel, the existing custom hooks and supporting DLLs were integrated into the automation framework. algoQA then generates automation scripts that combine standard automation functions with the custom functions, enabling seamless interaction with the proprietary controls while preserving the existing investment in automation. Examples cited: a microscope customer moved from Eggplant (considered flaky) to Python TestComplete; a CT customer moved from C# TestComplete to Python TestComplete, cutting automation time for one test case from about 5 days down to about 1 day; and an ECG customer migrated their application front end from Qt HTML to Qt QML, with algoQA generating scripts supporting both versions with minimal effort. algoQA leverages existing scripts, and for complex use cases involving custom logic, that logic can be integrated through algoQA's built-in code editor — a query can be written and code generated, which is then injected into the existing project. Code generation itself happens at the test-step level, which rolls up into test cases, scenarios, and features, and existing scripts can be integrated to support even complex custom functionality. Yes, If a step is common across multiple test cases and you modify it in one place, that change is reflected across all the other test cases that use it. Yes. There is a common folder that ships with a set of predefined utilities (e.g., for API handling, data reading, etc.). You can add your own custom utilities into this structure, and from that point on they are automatically included as part of subsequent script generation.

Frameworks & Scripting