Frequently Asked Questions

• How does algoQA work?
  With algoQA, all you need to do is profile the application under test and design tests using the profile of the application using simple drag & drop UI widgets. Profile is an offline model of the application under test. Once you have profiled and designed tests then algoQA produces Gherkin-based Feature Files and readily executable scripts.
  Profiling is the only manual effort and it is easy for the users to understand.
  
  
• How is the locator storage process handled, and how does DOM scraping work? 
  DOM scraping, also known as web scraping, is the process of extracting data from a web page or application using tools like algoScraper. This tool is used to capture all UI elements and their corresponding XPaths present on a web page or application, our tool is able to scraper complex DOM elements such as Shadow DOM elements. 

  These Locators will be stored in the centralized Object repository in algoQA.

  
  
  
• What applications and types of testing can be automated with your product?
  algoQA platform supports the automation of various applications and types of testing, which includes:
  

  Application: Web, Desktop, Mobile, and Hybrid, Robotic Process Automation (RPA) and Embedded Software.

  
  

  Types of testing: Smoke Testing, Sanity Testing, Regression Testing, Performance Testing, Load Testing, Release Testing and User Acceptance Testing. 

  
  

• Is algoQA compatible with different testing frameworks?
  algoQA supports test automation tools, such as Selenium, Protractor, Playwright, Cypress, Karate, Appium, Squish, Sikulix, FlaUI, WinAppDriver, TestComplete, and LeanFT.
  As algoQA supports Java and C# scripting, you can leverage RestSharp and RestAssured respectively for API automation in addition to Karate.
  It also supports execution engines, such as JBehave, NUnit, JUnit, TestNG, Cucumber, SpecFlow and Pytest.
  
  
• When we talk about test design, are we referring to both feature file creation and executable scripts? How are they connected? 

Yes, when discussing test design in the context of algoQA, we are referring to both the creation of feature files and the subsequent generation of executable test scripts. Feature files serve as the input for test automation, and they are transformed into test scripts by the platform. This process allows testers to design and execute tests based on the requirements, ensuring that the expected behavior of the application is thoroughly tested. 

algoQA supports various test design approaches including Prompt engineering, Online recording, Offline recording, feature file to scripts conversion, requirements to test cases and scripts generation .

• Does prompt engineering work both in offline and online modes? If an application is deployed and online, can it generate test cases from prompts, or do we need to record the steps? 

Prompt engineering works in offline as well as online model, algoQA model to be created with proper features and nodes to use Prompt engineering.

• How does auto-healing handle locator changes, complex/nested UIs, or elements appearing only after certain UI interactions? If two elements share the same ID but different indices, how is this handled? 

algoQA leverages LLM models to find the correct locators to heal the scripts. algoQA stores the locator information along with the parent DOM information, algoQA identifies the unique locators using this data.

• Where is expected data stored for verifying results? How does the tool compare actual UI outcomes with expected values, and how is environment-specific expected data managed? 

User has to input the expected data in algoQA and this tool has the capability to generate the combinatorial data sets based on business rules provided by the user, algoQA generates test data into separate TestData yml file. Environment specific data will be managed in the yml files.

• Can the framework handle Windows alerts/pop-ups, file uploads/downloads, and verify file contents? Can test validation include dynamic file or database data? 

Yes, algoQA handles windows alerts and file upload/download popups, our framework includes various utilities to verify the content including database data, PDF, Excel files.

What is alias step in algoQA?
If you wish to add a user-specific step or modify an existing step manually, then you can use alias step text box. For example, a login scenario where you want to add an alias step for verifying user profile details in the Dashboard, Feature file will be generated with alias step as And I verified the results in dashboard. You can use this functionality when you are adding manual steps. You can add a new step or edit an existing step.

• How can tests handle conditional flows or loops (e.g., when the workflow branches based on dynamic values)? 

Tests in algoQA can handle conditional flows or loops by using the FollowMe 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.  Users can inject their own code into algoQA framework to test dynamic workflows, algoQA Codebot can be used to create these custom functions.

• How does the tool manage reusing common modules (like login/logout) across different test cases? Will code be duplicated when recording? Can custom scripts/libraries be organized into folders? 

algoQA supports the reuse of common modules, such as login and logout, across different test cases through the use of custom scripts and libraries. This helps prevent code duplication. Custom scripts can be organized into folders within the platform for better management and structure. 

To create a custom script library, follow these steps: 

1.    Navigate to the Main Canvas and select the project in the Project Explorer pane. 

2.    Click on the More Menu (three dots) and choose "Code Editor" to open the Custom Setting Editor screen. 

3.    Create a new file with the desired name and file extension, then save the changes. The custom script files will be saved under the Utility folder, and you can create subfolders if needed. 

4.    Write your custom script code in the new file and save the changes. 

5.    To use the custom script in your test cases, import the file using the import statement at the beginning of your test script file. 

By organizing your custom scripts into folders, you can maintain a clean and structured test automation framework. This makes it easier to manage and maintain your test scripts over time.

• Can custom actions take parameters for reusable, flexible logic? 

Yes, custom actions can take parameters for reusable flexible logic. You can configure custom actions to accept parameters. Users can use algoQA Codebot and custom settings editor to provide reusable parameters.

• Can additional Node modules or libraries (e.g., for Excel validation) be integrated? What about using code from other languages? 

Yes, users can modify/add node modules by using the customize framework feature. we can use code from other languages, but it should be compatible with the existing language & framework.

• Can test data be decoupled from scripts, enabling data-driven testing (e.g., by YAML files per environment or per script)? 

Yes, test data can be decoupled from scripts in algoQA using the Data Decoupling option. This allows for data-driven testing and the use of separate YAML files for different environments or scripts. To use this feature, navigate to the Project Settings page, select the Data Decoupling option, and click Submit to generate a separate YAML file. Alternatively, you can use the Data Set option or upload an existing data set to generate test data in a separate YAML file.

• Can the tool validate that UI table data matches downloaded files, or vice versa (e.g., XML or CSV)? 

Yes, algoQA tool validates the UI table data with XML, CSV, Excel, PDF and other custom files.

• Tool updates 

  algoQA is committed to continuous improvement and innovation. We deliver regular enhancements, release notes, bug fixes, new features, and performance optimizations through monthly updates, ensuring our users always have access to the latest capabilities and a continuously evolving, robust testing solution.
  
  

• Do you produce UFT scripts?
  algoQA doesn't produce UFT scripts.
  
  

• Framework supports and capabilities that can be achieved using the tool 

  algoQA supports multiple frameworks and capabilities such as Selenium, TestComplete, Playwright, Rest Assured, RestSharp, Squish, WinappDriver, FlaUI, WebDriverIO, Appium, Cypress, LeanFT, Sikuli, JMeter, and more.
  
  

• Integration with CI/CD, JIRA, QMetry etc. 

  Yes, algoQA does support integration with DevOps Tools such as CircleCI, Jenkins, GitLab, Maven and ALM Tools such as Jira, TestRail, TFS, HPALM, and more.
  
  

• Version control repos support 

  algoQA accelerates automation by generating test scripts in the technology of your choice. These scripts can be stored in your version control or code repository tools.
  
  

• Cross browser execution 

  Yes, algoQA supports cross-browser testing with Chrome, Firefox, Microsoft Edge, Internet Explorer, Opera, and Safari.
  
  

• Integration with Test Management tool 

  Yes, algoQA supports integration with test management tools like JIRA, TestRail, HP ALM, ZOHO, and TFS.
   

• Is Parallel execution possible 

  Yes, parallel execution is fully supported. algoQA generates standard test scripts that can be executed in parallel using your preferred CI/CD tools or test runners (e.g., Selenium Grid, TestNG, JUnit, or cloud platforms like BrowserStack, Sauce Labs, etc.). algoQA itself is not required during execution.
   

• Is Test trigger schedule possible? 

  Yes, test execution can be scheduled and triggered automatically using CI/CD pipelines or job schedulers like Jenkins, GitLab CI, Azure DevOps, etc. You can integrate algoQA-generated scripts seamlessly into your existing automation workflow for scheduled or on-demand runs.
   

• Report formats 

  algoQA provides flexible reporting, offering standard file formats like HTML, XML, Word, PDF, and JSON, alongside specialized reporting templates such as Cucumber, Allure, and Extent, with options for custom designs.
   

• Is Customizable reporting possible

  Yes, algoQA allows you to design and generate custom reports tailored to your specific needs.
  
  

• Defect Integration for any failure 

  Yes, with algoQA, defect management tool integration is possible. Whenever a test case fails, algoQA can create or update defects in defect management tools like JIRA by capturing relevant details such as logs, screenshots, and test data.  
  
  

• Modular scripts ? 

  algoQA scripts follow the BDD framework and the Page Object Model (POM). Each script includes step definitions, workflows, pages, and objects. Test data can be included within the feature files or maintained in separate feature files.
  
  

• Object repo maintenance 

  algoQA supports auto-spying through algoScraper, which is available for web, mobile, and desktop applications. algoScraper helps in fetching objects, and also supports re-scraping to maintain them. Additionally, the auto-healing feature automatically handles object changes.
   

• Reusability for scripts and data 

  Yes, the existing scripts generated by algoQA are reusable even when there are application changes. Simply make the necessary modifications to the profile and re-generate the affected test cases and scripts. 

  
  

  Additionally, algoQA allows full customization and extension of test scripts through: 

  
  

  Custom Actions: Create custom actions to meet specific testing requirements. 

  
  

  Configuration: Upload existing test scripts and files, generate new ones, and organize them as needed. 

  
  

  Coordinate-Based Testing: algoQA supports coordinate-based testing for scenarios where traditional locators are not available or applicable. This is enabled through integration with tools like Sikuli, Squish, and TestComplete. 

  
  

• What operating systems, browsers, and devices can algoQA test against.
  algoQA supports the following: 

  • Operating systems:  Windows, Linux and Mac operating systems.  

  • Browsers supported:   Chrome, Microsoft Edge, Firefox and Safari for cross- browser testing

  • Devices: When it comes to handheld devices, algoQA supports both android and iOS devices.
    The devices could include TV as well.
    
    

• What development methodologies does your platform support?
  algoQA supports Test Driven Development (TDD), In-sprint automation and helps you realize continuous testing. algoQA is inherently Behaviour-Driven development (BDD) compliant. It also supports traditional development methodologies, such as the Waterfall model. Additionally, it accommodates various test cycles, such as Smoke Testing, Regression Testing, Release Testing, User Acceptance Testing, Performance Testing, Security Testing and Load Testing.
  
  

• How many test cases are generated by your platform? How much coverage will you provide for the test cases?
  algoQA offers two methods for designing tests: 

  • Follow Me feature for the users to design the test.

  • Auto test case generation capability. algoQA generates test cases for a given feature name based on user input

    algoQA provides comprehensive test coverage, including code coverage from third-party tools.
    
    
• How flexible is your platform to accommodate change in requirements?
  The platform accommodates: 

  • Workflow adaptation: Whenever there is a change in the workflow, that can be accommodated in the Profiling.

  • Handling corner cases:  Platform is extensible to cover edge scenarios.

  • Auto test case generation : Auto test case generation works by allowing you to specify the features that you want to include in a test case.

  • Auto- healing: algoQA platform provides an auto-healing feature helps in addressing locator issues caused by changes in the application being tested (AUT). 
    When the application being tested chang, the scripts may face issues locating specific elements. If this happens, the script might fail to execute. However, with auto healing feature enabled, it automatically identifies and fixes these issues with broken or changed elements. 
    

• Do you expect the user to have technical or test automation skills to use the platform?
  No, with algoQA anyone can test; business users, product owners, business analysts, developers or testers. No technical knowledge is required as there’s hardly any intervention required beyond profiling. And profiling is domain-intuitive and easy to use. That said, automation engineers and developers can write custom methods for incorporating any application specific logic.
  
  
• How do you assign data for each test case?
  To assign data for each test case in algoQA, follow these steps:

  • algoQA provides data generation capabilities, allowing you to create
    combinatorial datasets based on parameterized values. 

  • You can supply a number of datasets separated from the CI/CD pipeline.

  • You can also supply data in a third-party file.

  • algoQA allows you to maintain a clear separation between data and test cases,
    letting you store test cases in feature files (FF) and keeping data in a separate
    XML or test file.
    
    

• How is bulk data mapped to a set of test cases?
  For a scenario requiring combinatorial datasets, you can provide via a third-party file, such as .CSV file, to store and manage your datasets. To perform this, you can download the file in .CSV format and perform the bulk upload.
  To access the ‘Upload’ option, navigate to the Main Canvas > configuration folder > More Menu actions.

  Note that when uploading third-party files, they are scanned for viruses before the upload process is completed to ensure the file is safe and secure.
  
  

• Can requirements be translated to test cases or test scripts?
  Transforming requirements into Test Cases with algoQA:

  • Profiling serves as the initial step in the production of test cases and scripts.

  • People who are familiar with the project requirements can easily create test cases using algoQA.

  • Once test cases are designed, algoQA generates feature files (FF) and readily executable test scripts are produced. 

  • algoQA's test scripts are generated in your preferred technology and  can be executed from anywhere.
    
    

• Is there a possibility to reuse the steps?
  Yes. algoQA is all about reuse. It produces step definitions in such a way that they are reused across test scripts.

• Do I need to update algoQA project if I make changes outside algoQA. If so, how do I get the latest changes in algoQA project?
  Yes, changes made outside algoQA have to be manually updated in the offline model of AUT.  
  
  

• The system shall provide a secure, computer-generated, time-stamped audit trail to record the date and time of the operator entries and actions that create, modify or delete electronic records.
  Yes we will be able to provide audit trail
  
  

• The audit trail shall ensure that the original electronic record, along with the date and time stamp, is not lost and that the new record along with the date and time of the modification is recorded with a reason for change.
  Yes, AlgoQA maintains logs along with their corresponding timestamps.
  
  

• The system shall ensure data is retained/redily available for users to generate records in human readable and / or electronic form.
  Yes, we have backup and restore feature.
  
  

• The system shall protect records to preserve their content and meaning, and enable their accurate retrieval throughout the records retention period.
  Yes, data will be stored throughout the retention period.

• The system shall allow only Authorized Persons to certify the release of batches. The person releasing or certifying batches shall be clearly identified and recorded using an electronic signature.

  Security and Access Management Requirements

  
  Yes, Each build will follow algoQA release process
  
  

• The system shall ensure that passwords are not displayed during entry.
  Yes, it is protected
  
  

• The system shall utilize data encryption to ensure the authenticity, integrity, and confidentiality of electronic records from the point of creation to the point of their receipt.
  Yes, algoQA data is encrypted

• Where is Object repository?
  Object repository will be a part of the script generation. It can also be viewed and edited on the algoQA profiler.  
  
  

• Is it possible to reuse the existing scripts generated by algoQA if there are application changes?
  When there are application changes, make appropriate changes to profile and re-generate test cases and scripts. You can re-generate test cases and test scripts selectively, specific to the changes in the application.
  
  

• How can full Functionality coverage be ensured with algoQA?
  algoQA helps in identifying the impacted test cases for a given code change.
  
  

• Is it possible to verify test cases and segregate tests for a select list of modules?
  Yes, this can be done using algoQA. It is possible to create separate folders for different modules, you can have meaningful folder names for corresponding modules. You can also selectively generate test cases specific to application changes.
  
  

• Is it possible to resume from where I left off in case of an exception or application downtime?

  Yes, it is possible. During execution, when a test case fails or an application experiences an exception or downtime, the execution process will automatically proceed to the next test case, ensuring an uninterrupted testing workflow.
  
  

• Is it possible for multiple users to execute different modules of the same application concurrently?
  Yes. Test cases are segregated module wise and parallel execution is supported.
  
  
• Is it possible to test all the data entry fields for negative and boundary values successfully as a user?
  Yes. Field level validation is supported. The platform generates all negative datasets and boundary values.
  
  

• Is it possible to view the Test Execution Report day-wise, download and share with respective users?
  Yes, it is possible to view Test Execution Report day-wise, download it, and share it with the relevant users.
  
  

• Is it possible to choose a selective test case and prioritize the test execution?
  You can choose selective test case and prioritize the test execution: 

  • By grouping test cases using the 'Tag' option
    Use the 'Tag' option to group and categorize your test cases based on specific criteria. This allows you to prioritize the test execution by selecting and running test cases with specific tags, focusing your testing efforts on the important scenarios.

  • By pulling the selected test case scenarios:
    Select specific test case scenarios from the available pool based on their relevance to a particular testing phase, their importance, or specific testing objectives.
    Prioritize the test execution by pulling and including these selected scenarios in your test plan, excluding others that may not be immediately relevant.
    
    

• Is it possible to input the test data manually for field level validation? The system should be able to read the data from excel.
  The platform will generate multiple combinatorial data sets for field level validation.
  
  
• Can I integrate with Project Management/Defect Management and Code Repository tools?

  Yes. algoQA provides out-of-box integration with the test management, test data management, source-code management and defect management tools.
  
  

• Where are the test cases stored? Where is the test data stored? Is our test case and test data secured?
  Test cases and test data are stored in respective Application Lifecycle Management (ALM) tools that you are using.
  
  

• What ALM tools does algoQA support?
  HP ALM, TFS, ZOHO, TestRail and Jira.
  
  

• How does the tool handle and store data that are generated on the UI (e.g. Reference id)?
  We can store data in any of your ALM tools. It will be part of the test cases document.
  
  

• Do you have Multilingual tests capability - UI content validation when the web page is translated into another regional language?
  Yes, algoQA supports internationalization and localization.
  However, Test cases are generated in English like the Gherkin language and scripts are generated in the technology of your choice.
  
  

• Do you need access to our code?
  No, our testing is not invasive unless you want to do something with Unit testing.
  
  

• Is it possible to generate the test cases for the applications developed across various technologies ?
  Yes. algoQA platform is technology agnostic. It supports the following: Web services, green screen applications (including legacy systems and mainframes), supported UI Controls, multi-language scripting , multiple reporting formats to choose from, database support and modern web technologies.
  
  

• Is there a functionality to validate data migration through the algoQA platform? 
  ETL testing is not supported.
• Do we have to write Gherkin scenarios manually or are they generated? 

  No, You do not have to write Gherkin scenarios manually. algoQA automatically generates optimal test cases written in Gherkin language along with associated datasets and executable test scripts after you profile your application.
   

• Does algoQA support self-healing when locators change? 

  Yes, algoQA does support self-healing when locators change. It automatically detects changes in locators and adapts test scripts without requiring manual intervention. algoQA uses a combination of human and machine intelligence, including machine learning models, to identify application changes and heal the scripts, saving time, effort, and cost.
  
  

• How are the test scripts executed? Do we need to migrate to your infra? 

  There is no need to migrate the scripts to algoQA's infrastructure to execute them. Instead, you can download the scripts and execute them directly from the command prompt or anywhere.
   

• Do we own the test scripts? Can we modify them later? 

  Yes, You do own the test scripts generated by the platform and you can modify them later.  

  Key Point for Clarity: 

  • Test scripts generated by algoQA are in Gherkin language and are executable. 
  • Users can edit and modify these scripts to suit new testing requirements. 
  • algoQA is designed to allow easy updating and maintenance of test scripts. 
  • It supports reuse of test scenarios to increase efficiency. 
  • Scripts integrate seamlessly with CI/CD pipelines and can be maintained as part of continuous testing efforts. 
  • Thus, you have full ownership and flexibility over the test scripts created with algoQA.
    
    
    

• How do you ensure the prompts or AI-generated scenarios are relevant to our domain? 

  To ensure that AI-generated prompts or scenarios are relevant to your domain, you can: 

  • Review and edit the generated scenarios: After generating scenarios, carefully review them to ensure they align with your domain and make any necessary modifications. 
  • Provide custom data and configurations: Users can modify the data and configurations relevant to your domain when generating scenarios. 
  • Use domain-specific keywords and phrases: Incorporate domain-specific keywords and phrases in the AI's learning process to improve the relevancy of generated scenarios.
• How does algoQA work for mobile automation? Do you only support Android? 

  algoQA supports mobile automation comprehensively and is not limited to only Android devices. It provides automation capabilities across Android and iOS platforms for mobile apps and browsers. algoQA generates scripts for mobile automation using various tools/frameworks such as Appium, Squish and Playwright.
  
  

• Is Load and Performance Testing supported in algoQA? How is it done? If we are generating scripts in JMeter, does it have to be integrated in our system? 

  Yes, Load and performance testing is supported in algoQA just as algoQA can generate Java-Selenium scripts for UI automation or Java-RestAssured scripts for API automation, algoQA can produce Java-JMeter scripts for load testing.  algoQA supports URL based load test automation, API based load test automation.  algoQA can track page speed, page load time for web application and similarly for mobile application, we measure app performance using APIs.  
  
  

• Can the scripts generated by algoQA be integrated into Jenkins,GIT etc? 

  Yes, scripts generated by algoQA can be readily integrated with Jenkins, GIT, and other CI/CD tools, source code management tools, test management tools, defect management tools, and test execution clouds.
   

• Is integration with Oracle SQL available? 

  algoQA supports MySQL, SQL Server, MangoDB, PostgreSQL, AmazonRedshift and we can support Oracle if there is a need.
   

• What are the limitations of algoQA? 

  algoQA produces scripts using a technology of your choice, such as Selenium, Cypress, WebdriverIO, Appium, Squish, TestComplete, FlaUI, Karate, RestAssured, RestSharp, JMeter, and more. You can choose appropriate tools depending on the situation. algoQA can also combine these tools to address your needs.  

  
  

  For example, algoQA can combine WinAppDriver and FlaUI together to offer an effective framework for desktop automation. algoQA can combine Percy tool with Selenium to help with automation of visual regression. algoQA can combine WinAppDriver and Selenium to help with hybrid workflow automation. algoQA can also leverage COTS tools such as TestComplete and Squish.  

  
  

  There could be scenarios where none of these tools succeed and that becomes algoQA's limitation.  

  
  

  Additionally, algoQA does not supoort ETL testing.  
  
  

• What role does algoQA play in enabling or supporting test execution on cloud platforms like AWS, Azure? 

  algoQA accelerates automation and produces scripts in the technology of your choice.  The produced scripts can be executed anywhere on any of the execution clouds platforms like AWS, Azure, LambdaTest’s HyperExecute, BrowserStack, and others.
  
  

• Have you executed or tested any project on Google cloud? 

  Yes, one of our radiology informatics customers uses Google Cloud to execute scripts from algoQA.
  
  

• Can algoQA be integrated with an existing automation framework? 

  Yes, when the provided existing automation framework is open and flexible.
   

• Any experience with salesforce? 

  Yes, we’ve performed test automation for a product built on the Salesforce platform, specifically in the logistics space.
  
  

• Can an Existing issue be updated on JIRA? 

  Yes, you will be able to update issues as and when test case fails.
   

• Do we need to provide our credentials when passing parameters for JIRA integration? 

  Yes, credentials are required.  The password is used in the form of a time-bound access token to ensure security.
   

• Is Prompt Engineering compatible with A2A (Application-to-Application) communication and modular context handling? 

  Yes, Prompt Engineering is compatible with A2A communication and modular context handling.  

  Prompt Engineering in algoQA uses application-specific UI models—created offline via the algoQA Profiler—as input to derive BDD test scenarios using foundation models hosted on AWS Bedrock.  This automation approach aligns with A2A principles.  

  The modular context handling ensures prompt inputs are tailored based on the component context (e. g. , login vs.  payment), using only relevant metadata per test case.
  
  

• Support for the type of application like web/mobile/any specific tool like SAP/Pega/BY etc ?

  algoQA supports automation for web, mobile, and desktop applications. It is platform-agnostic and can be used for applications built on technologies such as Salesforce, SAP (e.g., SAP Fiori, SAP GUI), Pega, Blue Yonder (BY), and other enterprise tools. There are no limitations specific to the underlying platform or technology stack.
   

• Tool Cost licenses, infra and maintenance cost 

  Tool License Cost: 

  Overview	For Individuals  Freemium	For  Startups   Pro	For Business   Enterprise
  Cost	$ 0 USD /Lifetime	$ 250 USD/User/Month   (Billed annually)	Custom Pricing
  Number of Users	Individual	Upto 5 users	More than 5 users
  Number of Test Cases	15 per Month	Unlimited	Unlimited
  Number of Projects	Unlimited	Unlimited	Unlimited
  Web Automation	Java-Selenium	Yes	Yes
  Mobile Automation	No	Yes	Yes
  Desktop Automation	No	Yes	Yes
  API Automation	Java - RestAssured	Yes	Yes
  Load Test Automation	No	Yes	Yes
  ML Use Cases	No	Limited	Limited with Add-ons
  Storage	250 MB	Contact Sales	Contact Sales
  algoQA Academy	Limited Access	Full Access	Full Access
  Live Training	No	8 hours per user *	8 hours per user *
  Customer Support	Email	Email, Chat, Call	Email, Chat, Call

  For Detailed Pricing: Please visit, https://algoshack.net/pricing/
   

  Infrastructure Setup  

  Hardware Requirements
  
  

  Component	Requirement
  Memory (RAM)	16 GB
  Storage	- Type: 250 GB SSD   - Minimum: 50 GB free disk space for OS and apps   - Recommended: 100 GB or more (based on logs and data)
  Operating System	Windows
  Processor (CPU)	2.4 GHz quad-core or higher
  Network	1 Gbps network interface

• Software Requirements

• Component	Requirement
  Database Compatibility	MySQL and MongoDB
  Software	Node.js, Java, Maven, and Python

• Maintenance Cost: There are no maintenance costs for the tool since algoQA operates on a subscription-based model.
  
  
  

• Does algoQA support automating tests on virtual mobile environments? 

  Yes,  Execution can be done using virtual mobile environments.  For example, Appium scripts generated by algoQA can be executed on Android Studio emulators, simulators, and similar virtual mobile environments.  
   

• Will the tool be able to grow in terms of capabilities along with project ?

  Yes, algoQA can grow in terms of capabilities along with your project. There are two key ways this is achieved: 

  
  

  Extensibility through Custom Methods: The platform allows teams to write custom methods to extend its functionality. This means as your project evolves, algoQA can evolve with it, adapting to new requirements and supporting additional features as needed. 

  
  

  Support for Enhancements: We actively take up enhancements based on project needs. Whether it’s introducing new capabilities or refining existing ones, algoQA is built to scale alongside your testing strategy. 

  
  

  The platform is designed to be scalable and can be extended to support additional features and functionalities as needed. This includes the ability to automate the process of automation, reduce costs, and integrate with existing test automation solutions following open architecture.
   

• Learning curve for the existing team 

  algoQA has a minimal learning curve. Most users become productive within 2 to 4 weeks, depending on their familiarity with QA concepts. The intuitive low-code/no-code interface, guided onboarding, and in-product CoPilot support make it easy for testers and developers to get started quickly. 

   

  
  

• What is the channel or method used to share test feedback (defects/issues) with developers? 

  algoQA scripts can be executed locally or remotely, in sequence or in parallel, either immediately or on a schedule. These executions generate reports, which serve as feedback for developers. This feedback can be integrated into your test management tool, allowing actual results to sit alongside expected results for easy comparison. Not all test failures are application defects — they may be due to data, configuration, or script issues. Failures should be triaged, and only true defects should be logged in your defect management tool, as per your current process. 

  algoQA integrates seamlessly with: 

  
  

  Test Management Tools (e.g., TestRail, Xray for Jira) 

  Defect Management Tools (e.g., Jira, Zoho) 

  Test Execution Clouds (e.g., LambdaTest, BrowserStack, Azure DevOps) 

  
  

  For example, algoQA scripts can run on LambdaTest, and both test cases and execution results can be stored in TestRail, Xray, or Azure DevOps. When an issue is confirmed as an application defect, you can log it into tools like Jira with a single click. 

  
  

  A full list of supported integrations is mentioned in the image below.  

  
  
  
• Does one need coding experience to use algoQA?
  With algoQA, one does not require coding experience. 
  algoQA is a low-code/no-code platform that allows you to create test workflows with minimal coding. Most workflows can be built using the platform’s visual interface.

  
  

  However, depending on the complexity of your test cases, additional coding (around 10%) may be needed to meet specific requirements. This is an estimate, and the actual amount of coding required could vary.

  
  

  
  

  Technical Features

• What programming languages are supported by algoQA?
  C#, Python, Java, JavaScript, and TypeScript
  
  

• What security measures are in place to protect my data and tests?

  • Data Backups: Regular backups prevent data loss and ensure secure storage.

  • Access Control: Rules set by algoQA admin grant access to authorized users only to access the generated test scripts.

  • Customer-Specific Deployment is supported.

  • Session Management: Prevents simultaneous access with the same credentials, enhancing account security and data protection.
    
    

• Is it possible to create multiple feature files?
  You can create multiple Feature Files in the following cases:

  • Individual test case in a Feature File.

  • Test cases related to one module in one Feature File. 

  • Different modules are in different Feature Files.
    
    

•  Where can a user update the object IDs?    
  A user 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: Proactive approach to handle changes in object IDs or locators, ensuring that the changes can adapt to application changes. For detailed information, see Auto Healing article. 

  • Edit Object Repository in the Profiler Feature: Access and modify object IDs in the Object Repository file within the Profiler feature. Changes made here will apply to all relevant scripts.

  • Within Scripts: Alternatively, users can update object IDs directly within scripts. However, note that these changes will be specific to the script.
    
    

• When there is a change in scenario, should the user generate new test cases and test scripts every time?
  You must modify the profile for the changes in the application and generate test cases to reflect changes. It is possible for the user to selectively generate the test case and test scripts for the given change.
  
  
• How can we identify DOM changes automatically — is there an inbuilt detection mechanism? 
  We have features called ReScraper & Locator Mapping to identify delta changes whenever an application undergoes changes. Auto Healing feature helps to fix the DOM changes.
  
  
• How can we integrate API validation with database verification in the framework? 
  To integrate API validation with database verification in algoQA, you can follow these steps: 

  1. Perform API automation using algoQA API Collection as described in the context. 

  2. After successful API validation, perform database verification by adding a parameter in the node configuration. 

  3. Create a new node for database verification in the Main Canvas. 

  4. In the Node in Palette pop-up window, click the Edit Icon to open the Control Panel List Window. 

  5. Add the required parameter in the Control Value text box. For example, if you add a UI element as DB Query, enter the parameter value as PostgreSql_#Query1:-<add your query>. Replace <add your query> with your actual query statement. 

  By following these steps, you can integrate API validation with database verification in the algoQA framework.
  
  
  

  
  
  

• Why are “Then” verification steps missing in some scenarios, and how can they be added? 

  In the provided context, the verification steps are explicitly mentioned in the example scenario for the Amazon user registration process. The steps include validating the OTP entered by the user and proceeding with the registration process if the OTP is valid. 

  If you want to add verification steps to other scenarios, you can follow the same structure as the Amazon registration example. Include the verification step(s) after the action that requires validation and before the next action in the scenario. 

  For instance, if you have a scenario where you want to verify the text displayed on a button after it is clicked, you can add the "Verify Text" action as shown in the "Validating Element Visibility with verify text Action" subsection. 

  If the context does not contain the specific information required to add verification steps, you cannot add them without making assumptions or inferences. In such cases, you should respond with: "The provided information does not cover this topic."
  
  

• What types of automation does algoQA cover?

  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.
  
  

• How does algoQA differ from traditional record and playback tools?
  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, users can begin with inputs like Wireframes and Swagger documents. Profiling 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.
  
  

• Can I generate test cases if I only provide the home page or partial functionality?

  To generate test cases with only the home page or partial functionality, you need to ensure that the feature and UI elements related to the partial functionality are selected in the Main canvas before clicking the "Generate" button. If the required elements are not selected, the test case generation might fail. 

  For home page testing, make sure the home page is the starting point for the scenario you want to generate test cases for. If the scenario involves partial functionality, ensure that all related elements are included in the selection. 

  
  

• What is the output after recording a scenario in algoQA?
  After recording a scenario in algoQA, you will see a 'Scenario created successfully' message in the Recorded Scenarios window. This indicates that the scenario has been saved.
  
  

• Can I choose the technology for script generation in algoQA?
  Yes, algoQA generates scripts in the preferred technology of the user.
  
  

• How does algoQA handle reusing existing automated test scenarios or scripts?

  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 "Follow Me" 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. 

  
  

  
  

• Does algoQA support deduplication of test cases?
  Yes, algoQA supports test case deduplication. To identify and remove duplicate test cases, navigate to the Test Case generated folder in the Project Explorer pane, select the 'De-duplicate' option, and follow the steps provided in the 'Deduplicate TestCases' pop-up window. The platform generates a report detailing the identified duplicates and the revised list of unique test cases.
  
  

• What does algoQA’s feature file quality report validate?
  The algoQA platform's Feature File quality report validates the syntax and structure of the Gherkin-based Feature Files. It checks for proper usage of keywords, correct indentation, and the presence of required elements such as Feature, Scenario, Given, When, Then, and Examples. It does not validate the functionality or behavior described in the Feature Files.
  
  

• Does algoQA provide test coverage reports indicating which scenarios or areas are covered or missing?
  Yes, algoQA provides comprehensive test coverage, including requirements traceability and code coverage for third-party tools. The platform generates test coverage reports indicating which scenarios or areas are covered during testing.
  
  

• Can algoQA migrate scripts from one framework/technology to another?
  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.
  
  

• How does algoQA help with maintaining automation over time?
  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.
  
  

• Can algoQA align newly generated test cases with an existing automation framework?
  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.
  
  

• What is the value add of algoQA compared to GitHub Copilot or Amazon CodeWhisperer for test automation?
  algoQA offers consulting and professional services for test automation implementation and optimization, in addition to its platform features. Unlike GitHub Copilot and Amazon CodeWhisperer, which are AI coding companions, AlgoQA focuses specifically on software testing and test automation. Its platform includes custom actions functionality and configuration options, allowing users to tailor their test scripts and extend the framework to meet their testing needs. Additionally, algoQA integrates with tools like Sikuli, Squish, and TestComplete for Coordinate-Based Testing, enabling testing in scenarios where traditional locators are not available or applicable.
  
  

• Can product owners or non-technical users contribute to test scenario creation?
  Yes, product owners and non-technical users can contribute to test scenario creation in algoQA. The platform is designed to be intuitive and easy to use, allowing anyone to modify profiles and generate test cases for changes in the application. However, if users require more advanced customization, automation engineers and developers can write custom methods for incorporating application-specific logic.
  
  

• How do product owners contribute to test scenario creation using algoQA?
  Product owners can contribute to test scenario creation in algoQA by using the Edit Scenarios workflow. They can view, add, search, and filter scenarios in the Edit Scenarios screen. To access this feature, navigate to the Main Canvas screen, open a project, and select "Edit scenarios" from the More Actions menu. Product owners do not need technical knowledge to use this feature, as it is domain-intuitive and easy to use. If multiple users work on the same scenario, the active user must save their changes before another user can edit it. In a centralized project, an admin can also uncheck scenarios being worked on by another user and generate test cases.
  
  

• How does algoQA record test scenarios?
  algoQA does not use Record and Play functionality to record test scenarios. Instead, you can begin the process of automation using algoQA even without writing any code for the application under test. You can start with the same inputs as the development streams, such as Wireframes and Swagger documents. To create a test scenario, you can use the Follow Me feature or edit it in the Edit Scenario Form and add custom tags for organization.
  
  

• How does algoQA help identify missing test scenarios?
  algoQA helps identify missing test scenarios through its requirement tracking and traceability features. By ensuring that all requirements are covered by test cases, it assists in identifying any missing test scenarios. Additionally, it can help identify impacted test cases for a given code change, making it easier to identify and address any new test scenarios that may be required.
  
  How does algoQA handle customers with security and access restrictions?

  algoQA implements several security measures to protect customer data and tests: 

  1.    Access Control: Rules set by the algoQA admin grant access to authorized users only to access the generated test scripts. 

  2.    Customer-Specific Deployment: Each customer's environment is isolated, ensuring data security. 

  3.    Session Management: Prevents simultaneous access with the same credentials, enhancing account security and data protection. 

  These measures help maintain the security and access restrictions for each customer using the platform.
  
  

• How does algoQA support ongoing automation project needs?
  algoQA supports ongoing automation project needs by allowing you to extend your existing framework using it in a Brownfield Environment. This means you can leverage algoQA to optimize and expand your existing test automation efforts. For detailed assistance and implementation, AlgoShack offers consulting and professional services.
  
  

• When we talk about test design, are we referring to both feature file creation and executable scripts? How are they connected?

  Yes, when discussing test design in the context of algoQA, we are referring to both the creation of feature files and the subsequent generation of executable test scripts. Feature files serve as the input for test automation, and they are transformed into test scripts by the platform. This process allows testers to design and execute tests based on the requirements, ensuring that the expected behavior of the application is thoroughly tested. 

  algoQA supports various test design approaches including Prompt engineering, Online recording, Offline recording, feature file to scripts conversion, requirements to test cases and scripts generation .
  
  

• Does prompt engineering work both in offline and online modes? If an application is deployed and online, can it generate test cases from prompts, or do we need to record the steps?
  Prompt engineering works in offline as well as online model, algoQA model to be created with proper features and nodes to use Prompt engineering.
  
  

• How does auto-healing handle locator changes, complex/nested UIs, or elements appearing only after certain UI interactions? If two elements share the same ID but different indices, how is this handled?
  algoQA leverages LLM models to find the correct locators to heal the scripts. algoQA stores the locator information along with the parent DOM information, algoQA identifies the unique locators using this data.

  
  

• Where is expected data stored for verifying results? How does the tool compare actual UI outcomes with expected values, and how is environment-specific expected data managed?
  User has to input the expected data in algoQA and this tool has the capability to generate the combinatorial data sets based on business rules provided by the user, algoQA generates test data into separate TestData yml file. Environment specific data will be managed in the yml files.
  
  

• Can the framework handle Windows alerts/pop-ups, file uploads/downloads, and verify file contents? Can test validation include dynamic file or database data?
  Yes, algoQA handles windows alerts and file upload/download popups, our framework includes various utilities to verify the content including database data, PDF, Excel files.
  
  

• How can tests handle conditional flows or loops (e.g., when the workflow branches based on dynamic values)?
  Tests in algoQA can handle conditional flows or loops by using the FollowMe 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. Users can inject their own code into algoQA framework to test dynamic workflows, algoQA Codebot can be used to create these custom functions.
  
  

• How does the tool manage reusing common modules (like login/logout) across different test cases? Will code be duplicated when recording? Can custom scripts/libraries be organized into folders?

  algoQA supports the reuse of common modules, such as login and logout, across different test cases through the use of custom scripts and libraries. This helps prevent code duplication. Custom scripts can be organized into folders within the platform for better management and structure. 

  To create a custom script library, follow these steps: 

  1.    Navigate to the Main Canvas and select the project in the Project Explorer pane. 

  2.    Click on the More Menu (three dots) and choose "Code Editor" to open the Custom Setting Editor screen. 

  3.    Create a new file with the desired name and file extension, then save the changes. The custom script files will be saved under the Utility folder, and you can create subfolders if needed. 

  4.    Write your custom script code in the new file and save the changes. 

  5.    To use the custom script in your test cases, import the file using the import statement at the beginning of your test script file. 

  By organizing your custom scripts into folders, you can maintain a clean and structured test automation framework. This makes it easier to manage and maintain your test scripts over time.
  
  

• Can custom actions take parameters for reusable, flexible logic?
  Yes, custom actions can take parameters for reusable flexible logic. You can configure custom actions to accept parameters. Users can use algoQA Codebot and custom settings editor to provide reusable parameters.
  
  

• Can additional Node modules or libraries (e.g., for Excel validation) be integrated? What about using code from other languages?
  Yes, users can modify/add node modules by using the customize framework feature. we can use code from other languages, but it should be compatible with the existing language & framework.
  
  

• Can test data be decoupled from scripts, enabling data-driven testing (e.g., by YAML files per environment or per script)?
  Yes, test data can be decoupled from scripts in algoQA using the Data Decoupling option. This allows for data-driven testing and the use of separate YAML files for different environments or scripts. To use this feature, navigate to the Project Settings page, select the Data Decoupling option, and click Submit to generate a separate YAML file. Alternatively, you can use the Data Set option or upload an existing data set to generate test data in a separate YAML file.
  
  

• Can the tool validate that UI table data matches downloaded files, or vice versa (e.g., XML or CSV)?
  Yes, algoQA tool validates the UI table data with XML, CSV, Excel, PDF and other custom files.
  
  

• How does algoQA typically onboard and engage with new customers?
  Upon completing the registration, the customer support team will reach out to you for initial hand-holding sessions to explore the product and get started with algoQA. No technical knowledge is required to use the platform. For detailed information on pricing plans, see Pricing Plans in the FAQs.
  
  

• Does algoQA provide test coverage linked directly to the application?
  Yes, algoQA provides comprehensive test coverage for applications. It supports various types of testing, including requirements traceability and code coverage for third-party tools. For more information, refer to the "Test Automation" section in the FAQs.
  
  

• Does algoQA emphasize consultancy or just product sales?
  algoQA offers consulting and professional services in the area of test automation and QA, in addition to selling the product. For more information on pricing plans and services, please refer to the Pricing Plans section in the FAQ document.
  
  

• How do you define the quality of test cases, especially in a TDD framework? 

  In Test-Driven Development (TDD), the quality of test cases is determined by several factors: 

  1.Completeness: Test cases should cover all possible scenarios, including edge cases and negative tests. 

  2.Independence: Each test case should be independent of other test cases, meaning that the outcome of one test case should not affect the outcome of another. 

  3.Maintainability: Test cases should be easy to understand, modify, and maintain as the codebase evolves. 

  4.Reliability: Test cases should consistently produce the same results, ensuring the stability and accuracy of the test suite. 

  5.Readability: Test cases should be well-written and easy to read, making it clear what is being tested and the expected outcome. 

  In the context of algoQA, you can create and manage test cases using the platform's features, such as the 'Follow Me' feature and the 'Auto test case generation' capability. These test cases can be designed based on project requirements and then transformed into test scripts using profiling and other features. By focusing on the quality of your test cases, you can ensure effective testing and maintain a robust test suite in your workflow.
  
  

• How exactly does the auto-healing feature work when a locator fails? 

  The auto healing feature in algoQA, when a locator fails, automatically attempts to find a new locator for the failed element based on its properties such as text, class name, or tag name. This new locator is then used to continue the test execution. The process of finding a new locator is performed dynamically during test execution. 

  To enable the auto healing feature, follow these steps: 

  1. After generating the script, download it to your local folder. 

  2. Open the folder where you downloaded the script. 

  3. Locate the ApplicationSettings.XML file and open it. 

  4. Set the auto-healing setting to True. 

  5. Save the changes you have made to the application settings file.
  
  
  

  
  
  

• If input data is insufficient, how does the LLM or data generation handle it? 
  Prompt engineering leverages LLM for test case generation, offline model is the input for Prompt engineering, proper input data is required for LLM model, otherwise users have to edit the test cases based on requirements.
  
  

• How is parallel execution configured for mobile tests? 

   To configure parallel execution for mobile tests using algoQA, follow these steps: 

  1. Ensure all dependencies, such as mobile device drivers and necessary tools, are installed and configured. 

  2. Navigate to the algoQA script generated folder for mobile tests. 

  3. Click to highlight the folder address bar and type 'cmd' to open a command prompt. 

  4. Retain the first command prompt open and launch a second command prompt from the same folder. 

  5. In each command prompt, execute the appropriate command for the mobile test case you want to run. 

  For example, if you have generated scripts for a login test case and a cart details test case for mobile tests, you can execute both test cases parallelly as described above.
  
  
  

  
  
  

• How do you handle unstable or highly dynamic DOMs in applications? 

  Handling unstable or highly dynamic DOMs in applications can be challenging during test automation. One approach to address this issue is to use dynamic locators and WebDriverWait with expected conditions. 

  Dynamic Locators: Instead of using static XPaths or CSS selectors, use dynamic locators that can identify elements based on their properties or text content. This approach can help in handling elements with unstable or changing IDs or classes. 

  WebDriverWait with Expected Conditions: Use WebDriverWait with expected conditions to wait for elements to appear or disappear based on specific conditions. This approach can help in handling elements that are loaded dynamically or appear/disappear during test execution. 

  algoScraper has the capabilities to get the optimal XPath for dynamics elements.
  
  

• In mobile automation, how do you handle locator readability for controls with generic names like ViewGroup? 

  For mobile automation, when dealing with controls having generic names like View Group, improving locator readability is crucial to ensure accurate identification and interaction. One common approach is to use additional attributes or context to uniquely identify the desired element. Here are some suggestions:
  
  

  1.Use Accessibility IDs: Accessibility IDs are a great way to locate elements in mobile automation. They are unique identifiers assigned to elements for accessibility purposes and can be used to locate elements in automation scripts. To set an Accessibility ID for a View Group, you can use the Android Developer Tools or Xcode (for iOS) to inspect the element and set the ID programmatically.
  
  

  2.Use XPath or CSS Selectors: XPath and CSS Selectors can be used to locate elements based on their position, attributes, or other characteristics. For ViewGroups, you can use their parent-child relationships, attributes, or other unique characteristics to create a more specific locator.
  
  

  3.Use Text or Label: If the View Group has a unique text or label, you can use it as a locator. This can be done using text-based selectors or by using the find Element(Byxpath("//android.widget.TextView[@text='Your Text']")) syntax for Android or similar for iOS.
  
  

  4.Use Image or Icon: If the View Group has a unique image or icon, you can use image recognition techniques to locate it. This can be done using image recognition libraries or tools like Appium's find Element By Class Name or find Element By XPath with image-based selectors.
  
  

  5.Use Custom Locators: You can create custom locators using various techniques like find Element By Class Name, find Element By XPath, or find Element By Accessibility Id. These custom locators can be based on the specific characteristics of the View Group, such as its position, size, or attributes. 

  Remember, the key to effective locator readability is to make them as specific as possible while ensuring they remain stable across different versions and configurations of the application.
  
  

• If any modifications are made in the downloaded script. Do the changes reflect in the Profile?
  No. Any changes made in the downloaded script do not reflect in the Profile. You must update the changes in the Profile to reflect new changes in the script. You can upload custom files if there are any changes made.
  
  

• How does algoQA function for application testing ?
  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 one that goes into the development streams, such as Wireframes and Swagger documents.
  
  

• Are algoQA scripts ready to execute in CI/CD pipeline?
  Yes, Scripts generated by algoQA are readily executable in CI/CD pipeline.
  For example, you can leverage CI/CD environments, such as Jenkins for nightly executions.
  
  

• If so, what CI / CD tools is it compatible with?
  Jenkins, Azure, Bamboo and GitLab
  
  

• How easy is it to integrate algoQA to be seamlessly integrated into continuous integration and continuous deployment pipelines.
  When scripts are generated in algoQA, they are not automatically executed within a CI/CD environment. By default, to integrate algoQA into a CI/CD pipeline, you need to use specific execution commands to run these scripts as part of the CI/CD process.
  
  

• How are objects fetched automatically in web automation, desktop automation and mobile app automation?
  • 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.
    
    

• At what stage of my testing maturity can algoQA be best integrated into the Testing process?
  The integration of algoQA into your testing process can vary depending on your testing maturity as follows:

  • In a Greenfield Environment: You can leverage algoQA right from the beginning of your project. This means you can use algoQA to define test cases, automate them, and establish a robust testing framework as your project progresses. You will be able to leverage algoQA for  In-sprint automation.

  • In a Brownfield Environment: You can extend your framework using algoQA provided that your existing framework is open and fast-track automation.
    
    

• Does algoQA perform end-to-end testing?    
  algoQA supports end-to-end testing and can handle UI, API, and database interactions within a single test case.
  
  

• Is it possible to edit and modify the generated script?
  You can either make profiling changes or edit the scenarios to regenerate test cases and test scripts.
  
  

• Is it possible to generate negative scenarios in algoQA?
  You can generate Negative scenarios by generating combinatorial datasets using an appropriate feature.
  algoQA allows writing negative tests using possible variants of valid and invalid data inputs. This approach creates stable and reliable negative tests for applications. You can mention specified values that lead to exceptions and assign corresponding error messages. It will also help users to identify errors and taking corrective measures.
  
  

• Is it possible to change the application URL in the generated script?

  • algoQA scripts generated follow 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. To access this, right-click on the appropriate configuration folder in the Project Explorer pane. In the Code Editor screen > Application Settings file > update the application URL.

  • 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 the Main canvas > select the gear icon.
    
    

• Is it possible to do headless execution of generated script in web automation?
  algoQA scripts generated follow organized folder structure.
  You can execute the script in headless mode by making the changes in the Application Settings file, which displays configuration and preference settings specific to a particular application. To access this, Upon generating scripts, navigate to the Code Editor screen > Application Settings file > update the BrowserType parameter to headless.
  
  
• Can I  view the evidence for Pass/Fail Test Cases? The System should be able to capture the screenshot. 

  • Yes, test results can be viewed, and screenshots can also be taken for future reference. algoQA supports different types of reports- Extent, Allure, Nunit, and Custom. These reports can be produced in XML, HTML, and Microsoft Word formats. Reports capture screenshots, video clips, and links to execution logs. 

  • You can capture screenshots by setting the rules in the Global Configurations file.
    After generating In the Code Editor screen, navigate to the appropriate configuration folder in your project.
    For example, in the Java Selenium scripts generated folder structure, refer to ApplicationsSettings. Xml file located at src / test/Java directory to set the rules.
    
    

• We already have a test automation solution in place, how is your platform different or useful?
  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 by algoQA provided your existing platform follows open architecture.
  
  

• How do I protect my existing test automation investments, if I use algoQA?
  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.
    
    

• Explain the extent to which users can customize and extend test scripts

  algoQA is extensible.

  • Custom Actions functionality: algoQA platform allows you to create custom actions to incorporate your application specific  testing requirements.

  • Configuration functionality: 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.

• What is Coordinate-Based Testing?

  Coordinate-Based Testing is an approach used in automated testing when applications don't expose traditional "locators" or automation IDs. In situations, where testability considerations are not incorporated into application's architecture, particularly in legacy or green screen applications. algoQA integrates with  tools like Sikuli, Squish, and TestComplete, supporting Coordinate-Based Testing allowing users 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.
  
  
  
• Are you producing Python APM scripts or Java for Appium?
  The context provided discusses the installation steps for setting up Appium Settings using the Appium desktop app for both Python and Java. Based on the context, I cannot determine if Python or Java Appium scripts are being produced. However, I can provide you with information on how to set up Appium for both Python and Java. 

  
  

  For Python: 

  Open Appium desktop app and click the “Start Server v1.13.0” button. 

  Download and Install Appium Inspector. 

  In Appium inspector, set desired capabilities for a mobile app. 

  Start the session. 

  Verify that your emulator is running correctly. 

  
  

  For Java: 

  Open Appium desktop app and click the “Start Server v1.13.0” button. 

  Download and Install Appium Inspector. 

  In Appium inspector, set desired capabilities for a mobile browser. 

  Start the session. 

  Verify that your emulator is running correctly.
  
  
  

• Does algoQA replace frameworks like Appium or Selenium?
  No, algoQA does not replace Appium or Selenium. Instead, it supports their integration for mobile and web automation respectively. You can use these testing frameworks with algoQA to enhance your testing capabilities.
  
  

• Are Python Appium scripts manually coded today?

  No, the Python Appium scripts are not manually coded today. Instead, you can generate them using the algoQA platform by following these steps: 

  
  

  Navigate to the algoQA Platform and sign in with your credentials. 

  In the Main Canvas, click the "Generate Script" button and follow the onscreen instructions to generate the scripts. 

  After generating the algoQA scripts, navigate to the script downloaded folder to open the Application Settings File. 

  Update the details manually in the Application Settings file as shown in the example table. 

  Navigate back to the script directory and run the following command to execute the script:behave -f allure_behave.formatter:AllureFormatter -o <output_directory> <script_directory>\features\ 

   

  Replace <output_directory> with the desired output directory and <script_directory> with the directory containing the generated scripts. 

  
  

• Does algoQA support auto healing? Does it help with script failures due to element changes?
  algoQA does not have a built-in auto-healing feature for script failures caused by element changes. Users need to manually update the scripts when elements change in the application under test. However, algoQA's user-friendly interface and support for various testing frameworks make it easier to maintain and update scripts.
  
  

• Which frameworks does algoQA support for Linux and MacOS desktop automation?
  Python Sikuli framework is compatible with Linux and MacOS for desktop automation. For more details, refer to the Desktop Automation execution environment columns for Linux and Mac.
  
  

• Are these automation frameworks open source or paid?
  Some of the automation frameworks mentioned in the context, such as Selenium, Sikuli, and Appium, are open source. Others, like TestComplete and LeanFT, are commercial products. It's essential to check the specific framework's documentation or website for licensing information to determine if it's open source or paid.
  
  

• How does algoQA handle locator issues with shadow DOM or iframe elements?
  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.
  
  

• Can algoQA handle changes in application flow with auto healing?
  Yes, algoQA's auto-healing feature allows the platform to adapt automation tests to match changes made to the application.
  
  

• What platforms does algoQA support for features like auto healing?
  algoQA supports various platforms for its auto-healing feature, including web services, green screen applications, and modern web technologies. For more details, refer to the "Frequently Asked Questions" document under the "Flexibility and Extensibility" section.
  
  

• How are test cases designed in algoQA?

  algoQA offers two methods for designing tests: 

  
  

  Using the Follow Me feature, users can design the test. 

  Utilizing the auto test case generation capability, algoQA generates test cases based on a given feature name and user input. 

  
  

• So even for iOS devices, say an iPhone, are test cases and scripts generated manually or automatically?

  For iOS devices, test cases and scripts can be generated automatically using the algoQA platform. The process involves navigating to the appropriate folder in the Script Generation screen, selecting the required files under the Test Cases folder, and clicking the Analyze button. After that, you can proceed to generate the scripts by clicking the Proceed button and then the Generate Script button. The generated scripts can be downloaded to your local folder and executed using a terminal window. 

  
  

  Additionally, for mobile app automation using Python Squish QT (QML), test scripts can also be generated automatically after generating test cases. In this process, you need to navigate to the script generation screen, select the appropriate folder, and click the Analyze button to generate the scripts, which can then be downloaded and executed. 

  
  

• How to decide what user flows to capture for automation from web pages scraped?

  Deciding which user flows to capture for automation from web pages scraped depends on the specific requirements of your testing project. Consider the following factors: 

  
  

  Business Value: Identify the user flows that have the most significant impact on your business or user experience. 

  Frequency: Focus on user flows that are frequently used or executed during testing. 

  Complexity: Prioritize user flows with a higher level of complexity, as they may require more thorough testing. 

  Risk: Test user flows that have a higher risk of introducing bugs or issues. 

  Coverage: Ensure that all essential user flows are covered in your automation suite. 

  
  

  To get started, you can use the following steps: 

  Understand the Application: Familiarize yourself with the web application and its user flows. 

  Identify Key User Scenarios: Determine the most critical user scenarios based on business value, frequency, complexity, and risk. 

  Create a Test Plan: Develop a test plan that covers the identified user flows. 

  Implement Automated Tests: Use the algoScraper tool to extract the necessary UI elements and create automated tests for the user flows. 

  Maintain and Update Tests: Regularly review and update your automated tests to ensure they remain relevant and effective.
  
  

• What if the application changes and flows get updated? Will scripts auto heal and update?
  Yes, algoQA's auto healing feature can help adapt to application changes and update object IDs or locators as needed. This ensures that scripts remain functional even when the application's UI elements change. For more information, refer to the "Auto Healing" section in the FAQ document.
  
  

• How does the algorithm pick the steps for the appointment scenario?
  The algorithm generates test steps based on the elements scraped from the UI and the high-level screens selected (e.g., login, home, doctor, appointment). Initially, results may not be 100% accurate, but with model training and manual edits, future accuracy improves.
  
  

• How can we verify specific data, like the number of doctors for a dental appointment?
  You can define test case steps to check specific features such as filters or doctor listings, using predefined actions like “verify content” or “verify doctors”. The platform allows test design customization for such checks.
  
  

• How does algoQA handle drop-downs with multiple values and permutations?
  By providing multiple options in the input feed for a drop-down field, the platform generates all relevant permutations automatically; you instruct it using specific notations or input conventions.
  
  

• Does the healing procedure update the elements in the scraped repository?
  Yes, if an element is healed during execution, the update is reflected in the object repository and can be pushed back to version control (e.g., Git), maintaining synchronization with ongoing CI/CD usage.
  
  

• What automation tools are you using — or which technologies does algoQA support?

  • algoQA is GenAI-driven Low code / No code software test automation platform that seamlessly integrates with a wide range of tools, frameworks, and technologies to support diverse QA needs. 

  • It is compatible with popular test automation frameworks such as Selenium, Appium, Squish, Cypress, LeanFT, Karate, Playwright, RestSharp, RestAssured, WinAppDriver, Sikuli, webDriver IO and JMeter.  

  • The platform supports scripting in Java, C#, Python ,JavaScript and TypeScript, offering flexibility for different development environments.  

  • For execution, algoQA integrates with leading cloud platforms like BrowserStack, AWS, SauceLabs, kobiton ,AWS , Azure and Lambda test   

  • It also connects with ALM tools such as JIRA, TestRail, ZOHO and TFS for efficient test management and traceability. 

  • algoQA also supports multiple databases and reporting formats, including Amazon Redshift, MySQL, MongoDB, Cucumber, Allure, Extent, HTML, PDF, Custom, XML, and Word, enabling seamless data management and comprehensive reporting. 

  • Additionally, algoQA supports a wide range of reporting and execution engines, including JBehave, NUnit, JUnit, TestNG, Cucumber, SpecFlow, and Pytest, providing comprehensive visibility and flexibility in test execution and reporting. 

  • algoQA also integrates with popular DevOps tools such as CircleCI, Maven, GitHub, Jenkins, and GitLab, enabling continuous integration, seamless automation, and efficient CI/CD pipeline execution. 

   

• Can algoQA work with Microsoft Dynamics 365 ERP?
  Yes, algoQA can work with Microsoft Dynamics 365 ERP as it supports various testing frameworks and tools, including those for web and API automation.
  
  

• Does your Copilot feature connect with Microsoft Copilot?
  algoQA's Copilot is an internal AI assistant within the platform, not linked with Microsoft Copilot. It assists users in creating, executing, and analyzing test cases within algoQA.
  
  

• Can we automate both Web and Mobile applications in a single flow?
  Yes, algoQA supports combined multi-platform automation. You can create test scenarios that start on a web application and continue on mobile devices, enabling end-to-end omnichannel testing.
  
  

• Is algoQA compatible with our existing Selenium Java framework?
  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.
  
  

• Can algoQA support automation across our 23 applications — including POS, Mtouch, and e-commerce
  Yes, algoQA can handle multiple application environments and automate testing for Windows-based mobile apps (POS), Android, iOS, and web portals (e-commerce) under a unified framework.
  
  What types of platforms does algoQA support?
  algoQA supports the following types of platforms for testing:
   Web, Desktop, API, Mobile ,Hybrid, Robotic Process Automation (RPA), Embedded Software
  
  

• Can you explain impact-based testing? How does algoQA suggest which regression test cases to run after a change?
  Impact-based testing is a testing strategy that focuses on identifying and executing test cases that are most likely to be affected by a change in the application. algoQA suggests which regression test cases to run after a change using the following methods:
  1.    Test Impact Analysis: algoQA performs test impact analysis to determine which test cases are most likely to be affected by a change. This analysis is based on the relationship between the changed component and the existing test cases.
  2.    Test Prioritization: algoQA prioritizes test cases based on their impact and importance. Test cases that have a higher impact or are more critical are given priority.
  3.    Test Automation: algoQA's auto test case generation capability generates test cases for the changed feature based on user input. These test cases are executed to ensure the functionality of the changed component.
  4.    Test Execution: algoQA executes the prioritized test cases to verify the application's functionality after the change. The test results are reported, and any failed test cases are flagged for further investigation.
  
  

• Does algoQA support both functional and performance testing? Is this integrated or a wrapper over existing performance tools (like JMeter)?
  algoQA supports both functional and performance testing. It integrates these testing types within the same platform, allowing you to perform functional testing and performance testing in a single test case. However, it does not provide a wrapper over existing performance tools like JMeter. Instead, it offers its own performance testing capabilities.
  
  

• Can algoQA automate conversion from Ruby/Python scripts via feature files?
  Yes, feature files from Ruby can be used to auto-generate efficient Python scripts with optimized approaches, rather than just direct code translation.
  
  

• Can existing automation be imported/translated without rebuilding everything?    
  Yes, existing automation artifacts like feature files/scripts can be imported, translated to new languages (e.g., from Ruby to Python), and optimized without rewriting from scratch.
  
  

• How does algoQA integrate with enterprise cloud models (e.g. on-site Azure, spectrum GPT models)?
  The solution supports fully on-prem or hybrid cloud deployment, integrating enterprise LLMs (Azure, spectrum GPT), keeping all automation data and models within Charter’s secure perimeter.
  
  

• How does algoQA manage multi-framework scenarios, passing execution between different tools (e.g. Selenium/Tosca)?
  Scripts authored in one framework (like Selenium) can pass execution and data to other automation tools (Tosca, SmartBear), supporting distributed testing across Charter’s diverse solution landscape.
  
  

• How can teams quickly review large-scale batch test results and healing actions overnight?
  Custom and Cucumber reports provide summaries of script runs, healing actions, failures, logs, screenshots, and videos, supporting roll-up and overview for large overnight test batches.
  
  

• How does algoQA support test design and execution?
  The platform enables offline/online scenario recording, prompt engineering, conversion from legacy feature files, and defect-driven test creation. It produces scripts and automates execution across platforms.
  
  

• Are changing environments and auto-healing managed?
  Yes, algoQA features auto-healing scripts for locator/label changes, allowing stable operation across different environments (dev, staging, UAT, prod).
  
  

• What governance and partnership models are used?
  Formal partnership frameworks are offered—monthly governance calls, business opportunity reviews, consultative support, and co-development as needed.
  
  

• What support is available for migration from Ruby to Python?
  Migration is achieved by converting BDD feature files rather than scripts, provided both platforms are supported.
  
  

• What consultative and lab services does AlgoShack provide?
  Lab setup, independent consulting, and three-party deals (with partners like Genpact) tailored for enterprise needs and GenAI adoption guidance.
  
  

• How does AlgoShack handle enterprise data privacy concerns with GenAI?
  algoQA can be deployed in the customer’s own environment (such as AWS VPC) so no business data leaves the corporate firewall; multi-tenant SaaS is optional.
  
  

• What SaaS and consulting engagement models are available?
  algoQA is available as freemium, pro, or enterprise SaaS; consulting and “automation as a service” for wider implementation, including partner/co-development and lab setup.
  
  

• What platforms and automation models does algoQA support?
  UI, API, load, web, desktop, mobile, hybrid apps, and multi-app workflows are all supported in a single platform.
  
  

• Is test scheduling and continuous testing supported?
  Yes, algoQA supports scheduled and overnight test execution, report generation, and ensures tests run without manual intervention for 24/7 coverage.
  
  

• Can algoQA optimize and deduplicate feature files?
  Yes, it can assess the quality of feature files, detect duplications, and help merge similar tests for more meaningful automation.
  
  

• Does algoQA generate test scenarios directly from code in the CI/CD process?
  Yes, algoQA identifies test gaps and suggests new scenarios by checking developer code throughout the CI/CD process, ensuring scientific coverage and continuous improvement.
  
  

• What does AlgoShack do and what is algoQA?
  AlgoShack focuses exclusively on test automation; algoQA is a GenAI-powered, low-code/no-code automation platform producing scripts in any tech stack and boosting productivity by 10–20x over traditional methods.
  
  

• Does algoQA require direct code access for impact-based regression testing, and how is this achieved securely?    
  Only impact-based testing uses code analysis, leveraging trusted static code analyzers. Auto-healing and routine scenario automation remain non-invasive, typically requiring only UI/URL access.
  
  

• Can auto-heal log/document the changes made so teams can track script updates?
  Yes. Auto-heal changes are tracked in test reports so users can review any automated script edits, changes, failures, and healing events—this supports audit trails and overnight batch test management.
  
  

• How does algoQA auto-heal scripts after UI changes without code access?
  Auto-healing works by detecting locator/label changes during execution. Failed script runs trigger automatic fixes, updating the script repository where possible, with major design changes flagged.
  
  

• Can algoQA convert legacy scripts from older stacks to new tech (e.g. Ruby/protractor to Python/Webdriver)?
  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.
  
  

• Can the platform support UI-level, API-level, and performance testing?    
  Yes, algoQA supports UI, API, and load/performance testing and can intertwine scenarios between these layers.
  
  

• What are the limitations in backend code analysis for API test case generation?    
  Most approaches are non-intrusive and black-box; direct code analysis is used only for coverage and missing test cases, but scenario-based black-box interactions are preferred.
  
  

• How does algoQA accelerate automation and reduce manual maintenance?
  Uses AI and auto-healing for changes in the application (locators, labels, etc.), minimizing manual script maintenance and optimizing existing scripts for new environments.
  
  

• Is algoQA cloud-only, or can it run inside company firewall?    
  It can be deployed in-house within a firewall for privacy, with options for local or approved cloud LLMs (e.g., AWS foundational services), ensuring data privacy and organizational control.
  
  

• How does algoQA compare with Postman for API testing?
  algoQA offers scenario-based API automation similar to Postman but integrates UI and API, allows scenario chaining and script generation in multiple languages, and can save/download logs and results for CI integration.
  
  

• Is it possible to save download logs and responses from API executions?    
  Yes, algoQA allows saving logs, screenshots, video clippings, and API responses. Executable scripts can be generated and saved for integration with other tools.
  
  

• How does algoQA capture backend (API) calls from UI interactions?
  algoQA mostly captures UI workflows; API calls from UI can be logged via network browser tools, and API validations can be integrated as additional checks. Both UI and API can be tested and intertwined for scenario-based automation.
  
  

• What frameworks and coverage exist for web, desktop, ERP, and enterprise platforms?

  TestComplete framework is suitable for automating desktop applications, including ERP and enterprise platforms. It supports Python language and comes with built-in capabilities for Desktop Automation. Java-WinAppDriver and C#-WinAppDriver are other frameworks that can be used for automating Windows desktop applications using Java and C#, respectively. These frameworks are compatible with various databases like MySQL, PostgreSQL, and MongoDB. 

  For web desktop applications, Java-Selenium and frameworks like TypeScript - Playwright, Java Karate, and C# Selenium are compatible with MySQL databases. 

  If you're looking for specific coverage of ERP and enterprise platforms, please check the TestComplete documentation or contact Algoshack Technologies for more detailed information. 

  
  

  
  
  

• What makes algoQA unique compared to existing tools, and how does it help with initial development stages or productivity improvements?

  algoQA offers several unique features compared to existing tools, making it a valuable addition to your testing strategy: 

  1.    Automation of automation: algoQA allows you to automate the process of automation, enabling you to scale your testing efforts and reduce costs. 

  2.    Compatibility with existing solutions: You can extend your existing test automation platform by using algoQA, provided your current platform follows an open architecture. 

  3.    Support for various development methodologies: algoQA supports Test Driven Development (TDD), In-sprint automation, and Behaviour-Driven Development (BDD), among others. 

  4.    Customizability and extensibility: Users can customize and extend test scripts using custom actions, configuration functionality, and even integrate with tools like Sikuli, Squish, and TestComplete for Coordinate-Based Testing. 

  5.    Productivity improvements: algoQA helps improve productivity by offering continuous testing, allowing you to realize the benefits of continuous integration and delivery. 

  These features make algoQA a unique and powerful testing solution, especially during the initial development stages, as it allows for seamless integration with existing tools and methodologies while providing the flexibility to customize and extend your testing framework. 

  
  

  
  
  
  

• What is the licensing model after POC?
  AlgoShack offers flexible user-based subscription plans for algoQA. The Freemium model is available for free, and companies can access all subscription options, including Pro and Enterprise. In the Pro and Enterprise models, users can avail of a one-month trial period. For more information on subscription models, visit the Pricing page on the AlgoShack website. Additionally, AlgoShack proposes outcome-based engagement models where AlgoShack's engineers collaborate directly with your QA team.
  
  

• How does algoQA compare with Leapwork and Fireflink? We’re evaluating them too?

  algoshack offers the following advantages over Leapwork and Fireflink in algoQA: 

  •    GenAI-powered test creation 

  •    Multi-platform coverage 

  •    Auto maintenance 

  To experience these advantages firsthand, a 2-week free POC (Proof of Concept) has been proposed.  

  
  

  
  
  

• How are dynamic or unidentifiable elements handled, especially those lacking stable IDs or changing frequently?
  The platform supports multiple locator strategies such as parent, child, sibling relationships, custom XPaths, etc. If automated methods cannot resolve the element, manual locator entry is possible.
  
  

• How does auto-healing work when the application changes (e.g., locator changes)?
  Upon script failure due to locator changes or label modifications, agentic AI in algoQA updates the locator and re-executes the script. Updates are reflected in both the script and object repository, ensuring minimal manual intervention in such cases.
  
  

• How does the platform handle image elements in automation?
  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.
  
  

• How do you handle shadow DOM or iframe elements or missing locators?

  To handle shadow DOM or iframe elements or missing locators in algoQA, you can use the XPath Mapping functionality. Here's 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're 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. 

  
  
  

• How does algoQA handle batch execution of test cases?
  algoQA simplifies the execution of test cases in batches by allowing you to run multiple test cases together, either sequentially or in parallel. To organize test cases into batches, you can tag each test case with unique identifiers or labels using custom tags. These custom tags can be added while recording a scenario using the Follow Me feature or while editing a scenario in the Edit Scenario Form.
  
  Before executing batches, you need to ensure that all dependencies, such as browser drivers, libraries, and other necessary tools, are correctly installed and configured. You also need to ensure that environment variables are set correctly to access the required resources.
  
  algoQA generates scripts in your preferred technology.
  
  You can execute test cases in batches using the following methods:

  • Command Prompt Execution: Navigate to the directory where the scripts are saved and use the appropriate command to run them.

  • Jenkins Integration: Integrate with Jenkins, a popular automation server, to schedule and manage the execution of scripts as part of your CI/CD pipeline.

  • Third-Party Cloud: You can also execute the scripts in a third-party cloud environment, such as Lambdatest.    
    
    

• Auto Test Case Generation
  algoQA produces Feature Files without requiring test design by algoQA. The Auto Test Generate feature integrates with component-based design. When Feature Files are edited and saved, algoQA learns from the changes made and suggests subsequent Test Cases. For more information, refer to Auto Test Case Generation article.
  
  
• How does algoQA handle script generation and execution?

  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.
  
  

• What is database testing?
  Database Automation Testing is a software testing that focuses on ensuring the accuracy, completeness, security, and performance of databases within an application or system. By automating the testing process, users can efficiently verify the data integrity and identify potential risks before they escalate into major issues. 
  
  

• Is it possible to modify an individual API Request similar to Postman collection?

  You can modify the following details of an individual API requests within an API collection:

  • Endpoint URLs: Update the URL for the API endpoint.
  • HTTP Methods: Change the HTTP method by selecting appropriate option from the drop-down list. (GET, POST, PUT, DELETE, PATCH and OPTIONS.).
  • Headers: Edit or add HTTP headers.
  • Parameters: Modify query parameters or path variables.
  • Body: Change the request body (for POST/PUT requests), including data formats like JSON, form-data, or raw text.
  • Authorization: Update authorization settings, such as tokens or API keys.
  • In Postman, Pre-request scripts functionality is used to run custom scripts before API requests are sent. They run in the context of the request, allowing you to modify request parameters, headers, or body content dynamically. Same functionality can be used in algoQA API collection by writing custom methods. For example, API token authentication and configuring environmental variables.
    
    
• When searching for a smartphone on an e-commerce application using the keyword "Galaxy," how can I write an XPath to handle dynamic results where it's uncertain whether "Galaxy 23" or "Galaxy 24" will appear first?
  You can use common XPath expression while scraping elements. For more information on scraping common XPaths, refer to algoScraper as an extension article and update the locators using XPath Mapping feature.  For more information, see XPath XPath Mapping article.

• How can I migrate algoQA-generated scripts to my IDE and can the extension generate code within the IDE?

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. Where as, you can analyze the failures in the scripts. 

• Are there any limitations on the sites where algoQA and its browser extension can be used?
  The algoQA platform and its browser extension can only be used with the client's public sites. Any tools must be approved by the client before they can be used.
  
  
• Why do I need to whitelist the IP address for the installation of the algoQA and its browser extension?

Whitelisting the IP address is necessary for security. It ensures that only authorized systems can install algoQA and its browser extension, helping to prevent unauthorized access and ensuring the tool is used in a secure environment.

• Is framework also generated within the test scripts?

algoQA generates scripts in the automation framework of your choice like Selenium, Appium etc.

• How to add more test scripts once a test suite is generated?

If there are new test cases added to the test suite, scripts can be generated with those added test cases.

• How does AI/ML generates the Test data?

Test data is generated based on the scenario automated. 

• Do we have the option to scroll to the element and perform action?

Yes, algoQA extends the standard actions with options to create custom actions wherever required.

• In which part of the testing process do we extensively leverage AI?

Test design and Script execution.

• How does algoqa generates test cases? Do you need swagger or postman collection? 

algoQA generates test cases using API collections, which can be in Swagger/ postman collection or in Excel format. The API collection is uploaded to algoQA, and the platform generates the test cases and scripts. 

• What if our Swagger files are not well-documented or complete? We’ve seen that even tools like Postman/SwaggerHub struggle when the specs are weak?

Even if the Swagger files are not well-documented or complete, if we have proper working API's then we can use algoQA to generate test cases and scripts.

• How is algoQA different from chatGPT for script generation?

algoQA does not use AI to generate scripts.

•  Can I deploy your platform on-premise or in the cloud?
  You can deploy in your cloud infrastructure within your firewall, or you can use the cloud instance hosted by AlgoShack. The platform also supports on-premises deployment.
  
  

• What type of pricing model do you use for algoQA? What are pricing details about algoQA's pricing structure?
  The pricing model is SaaS (Software as a Service) based.
  The Pricing page displays pricing model details and breakdown of each model. For any details on pricing plans, get in touch with our sales team by clicking the Contact Sales button on the Pricing page, or you can reach out to the sales team using Contact Us feature.
  
  

• Detail the pricing plans, including any discounts for annual subscriptions or enterprise-level packages
  algoQA offers the following:

  • User-based subscription options:

    • Students: Access to the Freemium subscription only.

    • Companies: Access to all subscription options, including Freemium, Pro, and Enterprise.

  • Subscription models:

    • Freemium: In the Freemium model, users are entitled to a lifetime free subscription. For more information, see Pricing page.

    • Pro and Enterprise:  In the Pro and Enterprise models, users are entitled to a one-month trial period. For more information on pricing models, visit our Pricing page.
      AlgoShack does not offer any discounts. For any other information, contact the Sales team. 

      
      

• Is there a free plan available?
  AlgoShack provides three pricing models: Freemium, Pro, and Enterprise
  • Freemium model: AlgoShack offers a Freemium model where users are entitled to a lifetime free subscription. For detailed information, see Pricing page.
  • Free trials for Pro and Enterprise models : You can use the Free trials for Pro and Enterprise models. To access Free trials, in the Pricing page on the AlgoShack website, click the Free Trial button. 
  • Sales team: If you have queries about pricing, want to discuss the pro and enterprise plans, get in touch with the sales team using the Contact Us feature or Contact Sales button on the pricing page.
  • Customer support team: If you need additional assistance, get in touch with the customer support team at customer.support@algoshack.com.
    
    
• Can you provide demo links?

  Following are the demo links: 

  • Web Automation  

  • Desktop Automation  

  • API Automation when API details are captured from API collection 

  • API automation when API details are captured in a spreadsheet 

  • API Automation when API details are captured from algoQA forms 

  • Mobile Site Automation 

  • Mobile App Automation 

  • Load Test Automation 
    
    

• Is there a trial period for your platform; is it for 14 days or 30 days?
  Yes, AlgoShack offers a trial period. As of now, the trial period is one month for Pro and Enterprise subscription models.
  
  
• Can you provide case studies or success stories from your customers?
  Case studies: Customer experiences with algoQA

  • Digital Commerce 

    • Fashion and Retail: Elaborate coverage of third- party devices testing in a multi-brand marketplace environment, providing multi- browser support for desktop and mobile apps. 

    • Online Retail – Merchandise: End-to-End testing including automated test cases and test scripts for an online retail brand resulting in a 100% coverage and 80% savings of testing.

    • Online Retail – Jewellery: Leveraging algoQA for the testing and test automation of an online Jewellery brand’s portal along with a seamless migration to Magento.

    • Fashion and Lifestyle: With algoQA, covering website, mobile sites, mobile apps, virtual stores and hyperlocal testing for 11 brand portals for a retail giant, providing 97% coverage.

  •  Medical Devices
    • ECG Full Disclosure Module: Covering the test automation of Electrocardiogram (ECG) full disclosure module, reducing test cycle time by 75% and saving 70% cost.
    • CT Software Application: Leveraging algoQA for the computed tomography (CT) software test, not only automated testing but enhanced test coverage significantly.
    • CT Software Application -Leveraging algoQA, automated sanity for CT software faster and helped reduce license footprint.
      For more information, see Case studies.
      
      
  • What training and resources are available for users to get started?
    Getting started:
    When you subscribe to algoShack, you will get access to the training materials and instructional videos through algoQA Academy portal.
    Additionally, you will find helpful documentation in the algoQA Wikipedia.
    
    
  • Do you offer consulting, professional services, or support to assist with test automation implementation and optimizing the product?

    • AlgoShack offers consulting and professional services in the area of test automation and QA. Specially for assistance with algoQA, the services include free trial and  freemium plan. For detailed information, see Pricing Plans.

    • The registration process is online. Upon completing the registration, the customer support team will reach out to you. They will assist you in initial hand-holding sessions to explore the product and get started.
      
      

  • How can I get in touch with the sales team for more information?

    To contact sales team, you can: 

    • Reach out through the Contact Us button.

    • Click the Contact Sales button on the Pricing page.
      
      

  • Can you provide information about the verticals supported by algoQA?
    alogoQA is vertical agnostic. It covers use cases that span across various domains, such as retail and digital commerce, medical devices, third-party logistics, enterprise software, gaming and banking. The platform follows a domain-led approach for every vertical and is open to newer verticals.
    
    
  • How can we see the solution?
    You can see the solution in the following ways: 

    • Request or Book a Demo. 

    • Try Now 

    • Register and start using a freemium plan.

    • Free trials 

    • Register for  Pro and Enterprise plans. For more information, see Pricing Page.
      
      

  • How many days will you take to demo for an application of our choice?
    It takes a few days for a customized demo for your application after receiving access to your application.
    
    

  • Are you flexible to work out of your client's location, or in their time zone?
    AlgoShack provides flexibility in adjusting to different engagement models and time zones based on the client’s requirements.

  • Training and courses 

    algoQA provides extensive training and courses to ensure users are fully equipped to maximize the tool's potential: 

    algoQA Academy: All users gain access to the algoQA Academy, offering self-paced training modules that cover various testing aspects, including web, mobile, API, desktop, and load testing. This allows users to learn at their own pace and focus on areas relevant to their needs. 

    Live Training Sessions: Each user receives 8 hours of live training, providing interactive and hands-on experience with expert instructors. This ensures a solid foundational understanding and an opportunity for direct Q&A. 

    Ongoing Product and Technical Support: Continuous product and technical support is provided, with the level of support tailored to the selected subscription model, ensuring uninterrupted assistance for any queries or issues that may arise. 

    
    
    

  • Company and community Support for the tool 

    algoQA offers comprehensive support through multiple channels, ensuring users have all the resources they need for a seamless experience: 

    
    

    24/7 CoPilot and In-Product AI Assistance: An integrated CoPilot provides real-time in-product assistance to help users resolve issues instantly, right when they need it. 

    
    

    Dedicated Customer Support: For more complex issues or personalized guidance, users can directly reach out to our dedicated customer support team, available to provide timely and effective solutions. 

    
    

    algoQA Academy: Users can leverage the algoQA Academy for structured learning paths, tutorials, and courses designed to enhance their proficiency and understanding of the tool. 

    
    

    Comprehensive Wiki: A detailed algoQA Wiki serves as a rich knowledge base, offering in-depth documentation, FAQs, and troubleshooting guides for self-service support. 

    
    

    Handholding Sessions: Our Customer Success team conducts personalized handholding sessions, providing tailored guidance and direct support to ensure customers maximize their value from algoQA. 

    
    
    

  • Does algoQA platform provide content verification services?

    • algoQA platform is meant for intelligent automation of software testing, application and automation types. It supports the automation of various applications and types of testing, which includes: Application:  Web, Desktop, Mobile, and Hybrid, Robotic Process Automation (RPA) and Embedded Software.

    • Types of testing: Smoke Testing, Regression Testing, Release Testing, User Acceptance Testing, Performance
      Testing, Security Testing and and Load Testing.
      For more information, refer to our algoQA platform covers the test automation section.