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.
  
  
• 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.
  
  

• 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.
  
  

• 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.
  
  
• 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.
  
  
• 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.
  
  

• 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.

•  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.
    
    

  • 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.