algoQA is a platform with end-to-end automation and uses Artificial Intelligence (AI) to enhance its capabilities.
Key capabilities include:equest
Profiling the application, Dataset creation, Test case generation and Executable Test scripts.
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, Regression Testing, Release Testing, User Acceptance Testing, Performance Testing, Security Testing and and Load Testing.
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.
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.
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.
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.
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 requirements traceability and code coverage for third-party tools.
The platform accommodates:
- Workflow adaptation: Whenever there is a change in the workflow, that can be accommodated in the Profiler.
- Handling corner cases: Platform is extensible to cover exceptional or unusual 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.
Flexibility and Extensibility: The platform is flexible and extensible; You can add, modify or delete configurable elements to keep pace with changes in the application under test.
- Auto- healing: algoQA platform provides an auto-healing feature. It smoothly adapts automation tests to match the changes your team makes to the application.
Locator changes and Cosmetic alterations: algoQA can pick up any changes in the locators and other cosmetic alterations.
Click here for more information.
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.
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.
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.
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.
Yes. algoQA is all about reuse. It produces step definitions in such a way that they are reused across test scripts.
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.
algoQA helps you track requirements coverage. algoQA can also help identify traceability between requirements and test cases, and identify impacted test cases for a given code change.
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.
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.
Yes. Test cases are segregated module wise and parallel execution is supported.
Yes. Field level validation is supported. The platform generates all negative datasets and boundary values.
Yes, it is possible to view Test Execution Report day-wise, download it, and share it with the relevant users.
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.
The platform will generate multiple combinatorial data sets for field level validation.
The platform will generate multiple combinatorial data sets for field level validation.
Test cases and test data are stored in respective Application Lifecycle Management (ALM) tools that you are using.
HP ALM, TFS, GitHub, ZOHO, TestRail and Jira
We can store data in any of your ALM tools. It will be part of the test cases document.
Yes, algoQA supports internationalization and localisation.
However, Test cases are generated in English like the Gherkin language and scripts are generated in the technology of your choice.
No, our testing is not invasive unless you want to do something with Unit testing.
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.
ETL testing is not supported.
- 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.
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.
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.
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.
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.
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.
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.
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.
Jenkins, Azure, Bamboo and GitLab
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.
- 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.
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.
algoQA supports end-to-end testing and can handle UI, API, and database interactions within a single test suite.
You can either make profiling changes or edit the scenarios to regenerate test cases and test scripts.
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.
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.
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.
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.
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.
With algoQA, one does not require coding experience.
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.
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.
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.
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.
- 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.
To contact sales team, you can:
- Reach out through the Contact Us button.
Click the Contact Sales button on the Pricing page.
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.
It takes a few days for a customized demo for your application after receiving access to your application.
AlgoShack provides flexibility in adjusting to different engagement models and time zones based on the client’s requirements.
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 platform covers the test automation section.
You can deploy in your cloud infrastructure within your firewall, or you can use the cloud instance hosted by AlgoShack.
PRICING AND SUPPORT
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.
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 on limitations, 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.
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 firstname.lastname@example.org.
Following are the demo links:
Yes, AlgoShack offers a trial period. As of now, the trial period is one month for Pro and Enterprise subscription models.