Autify｜AI Platform for Software Testing

What is Autify?

Autify is an AI testing platform designed for software quality engineering, development, and QA teams. Its current offerings include the ability to execute tests using natural language, low-code and code-based testing with Playwright, AI-driven test design, automation of web and mobile applications, as well as professional quality assurance services.

Autify was initially known for its NoCode-based recording testing capabilities and AI-driven self-healing functions; it has since expanded to include product lines such as Aximo, Nexus, Genesis, and Mobile. The testing methods, platform coverage, and billing mechanisms vary significantly among these products, so it is necessary to evaluate each one separately when making a choice.

Product Line Overview

Aximo autonomous AI testing agent

Aximo allows users to describe in natural language the processes that need to be verified, with the AI then handling the operations on web, mobile, or desktop applications. It does not rely on fixed selectors or traditional testing scripts as its main methods of execution; as a result, there is usually no need to manually adjust the positioning details whenever the interface changes.

• Understand the objectives, prerequisites, and expected outcomes of natural language testing.
• Navigate through the pages, click, enter information, and complete tasks just like a real user would.
• During execution, the next step is determined based on the current interface.
• Verify whether the process yields the expected results and provide a clear report.
• It covers web pages, iOS, Android, macOS, as well as enterprise desktop environments.
• It supports tests such as email testing, visual regression testing, and operating system-level interactions.
• Choose between different models based on speed, reasoning ability, and integration overhead.

How to create tests using Aximo

1. Select the web page, mobile application, or supported desktop environment that you want to test.
2. Describe the starting point, the user’s goals, the key steps, and the expected results in simple and natural language.
3. Prepare a test account for isolation, reproducible data, and the necessary login information.
4. Select an AI model that is suitable for the task’s difficulty and cost.
5. Run the tests and observe the proxy’s navigation, input, and decision-making processes.
6. Examine the evidence of failure to determine whether it is due to product defects, environmental issues, or misjudgments by the agent.
7. Repeat the process after adjusting the description or test data to confirm that the results can be reproduced consistently.
8. Include scenarios for verifying stability in continuous regression and release checks.

Aximo scoring rules

Aximo consumes points based on the steps involved in AI testing; different models and platforms use different multiplication factors. More advanced models as well as testing on mobile devices typically require more points, while desktop testing falls under the Enterprise capabilities.

Aximo package prices

Differences in features of Aximo plans

Aximo script generation and MCP

Aximo can use MCP to provide the testing context to Claude, Cursor, Copilot, or other coding agents. These agents can then generate scripts using frameworks such as Playwright, Selenium, Cypress, or others; the resulting code becomes the property of the user and can be integrated into existing repositories.

• Quickly explore and validate user workflows using natural language.
• Convert the stable process into code testing that aligns with team preferences.
• After generating the script, continue with manual editing and review.
• Commit the code to version control and run it in the existing CI environment.
• Reduce reliance on proprietary testing formats specific to a single platform.
• MCP connections should restrict access to testing credentials and the internal environment.

What is Autify Nexus?

Autify Nexus is a modern test automation platform based on Playwright, which incorporates natural language recording, low-code steps, and full code editing. Users can use code-free assertions, JavaScript, or Playwright code within the same scenario, and they can import or export scripts.

• The natural language Recorder converts business descriptions into test steps.
• The low-code interface is suitable for QA and product teams to create scenarios.
• Most steps can be converted into Playwright code for further modification.
• It supports code-free assertions as well as custom code assertions.
• Trace and main logs are provided to help identify failures.
• It supports visual regression, test plans, folders, and tags.
• Use URL substitution to reuse scenarios in development, testing, and production environments.
• The paid plan supports script import and export, shared workspaces, and cloud parallel processing.

How to create regression tests using Nexus

1. Install the Nexus desktop environment and create a test project.
2. Select the local testing environment along with the Chrome or Edge browser.
3. Record core user workflows using natural language Recorder or low-code steps.
4. Add assertions for page status, text, elements, and visual results.
5. When precise control is required, convert the steps into Playwright code.
6. Executing and downloading Trace and log analysis locally failed.
7. Verify development, testing, and production pre-environments through URL replacement.
8. Paid teams can share scripts and integrate with cloud parallelization and CI processes.

Price of Nexus package

Price of Nexus additional features

The basic price of Nexus Professional does not represent the total cost of an entire team; users, shared workspaces, cloud concurrency, generative AI, and IP whitelists may incur separate charges. A formal purchase order should be based on a quote that takes into account the combination of team size and CI usage.

Nexus free version and full trial version

Nexus offers a free tier that allows users to experience its core local capabilities on a long-term basis, as well as a full-time limited trial version intended for corporate use in the context of PoC projects. The product page provides different details regarding the duration of this trial; once registered, the deadline shall be determined according to what is specified in the account settings and confirmed by sales.

Autify Genesis test design

Autify Genesis operates before the automatic execution phase; it is responsible for converting product requirements, specifications, source code, and uploaded files into structured QA assets. The team can review and modify the AI-generated outputs at each step, after which the test cases are sent to Nexus, Aximo, or other execution tools.

• Analyze product specifications, user stories, source code, and related documents.
• Organize the list of functions and the capabilities that need to be verified by the system.
• Generate test perspectives, risk areas, and coverage strategies.
• Create detailed test cases that include steps, data, and expected results.
• Generate test plans, QA documents, and assets that can be reused by the team.
• Manual editing is allowed at the functionality, perspective, and test case stages.
• Connect the confirmed use cases to automatic execution and autonomous testing.

Genesis usage process

1. Import authorized requirements, specifications, design documents, source code, or testing materials.
2. Have Genesis extract the functions and business behaviors, which are then verified by the product and QA teams.
3. Generate test scenarios and boundary conditions for high-risk functions.
4. Expand the concept into a use case that includes prerequisites, data, steps, and expected results.
5. Remove duplicate and low-value use cases, and add implicit rules known to domain experts.
6. Determine automation priorities based on risk, level, and scope of deployment.
7. Hand the selected use cases over to Nexus, Aximo, or manual testing for execution.
8. Update test design assets based on defects and production feedback.

Autify Mobile

Autify Mobile is designed for native iOS and Android applications; it helps teams record test scenarios and execute them in various mobile environments. It is suitable for teams that want to reduce repetitive manual testing efforts without having to write Appium code for each scenario.

• Automate the user workflows for native iOS and Android apps.
• Create and maintain mobile testing scenarios through intuitive operations.
• Use AI to locate changed interface elements and reduce maintenance efforts.
• Run regressions on various devices, systems, and environments.
• Integration with CircleCI, Jenkins, Webhook, TestRail, Slack, and others is supported.
• Include mobile testing results in the release and quality processes.

Traditional Autify NoCode

Autify NoCode enables non-engineers to record user actions through browser extensions or mobile apps, and save them as automated scenarios. AI self-healing attempts to reposition elements when their interface properties change, thereby reducing the need to maintain selectors.

• Record clicks, inputs, selections, navigation, and common business operations.
• Add text, elements, URLs, and other result assertions.
• Perform cross-browser testing using a combination of PC and mobile browsers.
• Use JavaScript steps to handle special logic.
• Use local playback to quickly resume recording or debug scenes.
• Access local or intranet applications via Autify Connect.
• Use the API or CLI to trigger the test and wait for the results.

The role and limitations of AI self-healing

AI self-healing will look for similar targets after changes in element attributes or page structure, thereby reducing failures caused by minor adjustments to selectors. It cannot guarantee that the business processes will remain correct, and it may also select similar but incorrect buttons as targets.

Testing environment and private applications

• The free and standard cloud solutions are executed in the Autify hosting environment.
• Nexus allows tests to be created and debugged first in the local desktop environment.
• Autify Connect enables NoCode Web connections to local or intranet websites.
• An IP allowlist is used to permit specific Autify sources to access restricted environments.
• Enterprise offers local, dedicated infrastructure, or options for local execution.
• Test accounts, keys, and data should be strictly separated from those of production users.

CI/CD and Integration

Appropriate use cases

• Release regression: Verify login, purchasing, payment, and core processes before each deployment.
• Cross-browser testing: Check how the webpage behaves in different browsers and with various settings.
• Mobile app regression: Covers key user journeys on iOS and Android.
• Autonomous exploration and execution: Use natural language to have Aximo verify processes that are constantly changing.
• Test design: Generate structured test perspectives from large specifications and codebases.
• Visual regression: Detecting changes in element styles, layout, and page appearance.
• Environmental reuse: URLs are used to replace environments for development, testing, and production.
• Continuous testing: Automatically enforce release gates via APIs, CLI, and CI tools.
• Script migration: Import, export, and continue maintaining Playwright code in Nexus.

Which teams are suitable?

• There is a lack of full-time automation engineers, but the QA team needs stable regression testing.
• It is hoped that QA and development teams will work together to maintain the engineering framework for Playwright tests.
• Companies that offer both web versions, mobile apps, and some desktop applications.
• Enterprise teams that need to develop test designs based on complex requirements and source code.
• Agile teams with frequent interface changes and high maintenance costs for traditional selectors.
• Developers who wish to transform the exploration of natural language testing into their own custom code scripts.
• Organizations that need consultant assistance to migrate and establish quality engineering processes.

How to choose Autify products

Costs other than price

• Test design: Define risks, coverage levels, and the scope that can be automated.
• Test data: Prepare repeatable accounts, orders, files, and environment settings.
• Use case maintenance: Update objectives, assertions, and expected results in response to business changes.
• Execution costs: points, cloud concurrency, devices, waiting time, and retry attempts in case of failures.
• Manual review: Determine whether the failure of the AI is due to a defect in the product or an incorrect decision by the agent.
• CI integration: Managing tokens, pipelines, timeouts, and release gates.
• Compliance and security: Management of credentials, isolation of personal information and production data.

Product advantages

• It also offers autonomous agents, the Playwright hybrid approach, and traditional code-free solutions.
• It covers various aspects such as test design, creation, execution, maintenance, and CI integration.
• Aximo reduces the burden on maintaining dynamic interfaces caused by selectors and fixed scripts.
• Nexus supports the import and export of scripts, thereby reducing the risk associated with locked formats.
• Genesis can convert large-scale requirements and source code into a QA structure that is suitable for review.
• It covers web, iOS, Android, and Enterprise desktop testing as well.
• Public APIs, CLIs, and official CI projects facilitate integration with existing toolchains.

Usage restrictions

• The functions of different Autify products overlap, so the team needs to clarify the testing methods and responsibility assignments first.
• Autonomous AI systems can make mistakes and exhibit uncertainty; it is not sufficient to consider only the result of a single attempt.
• Aximo consumes points according to specific steps and models; complex movement processes incur higher costs.
• Users of Nexus Professional, workspaces, cloud concurrency, and AI may be charged separately.
• Traditional AI self-healing may incorrectly match similar elements, leading to false approvals.
• Desktop testing, local deployment, and advanced enterprise controls require Enterprise.
• Automation cannot replace exploratory testing, usability assessment, and domain risk analysis.
• Strict security controls are required for testing credentials, production data, and access to private networks.

Implementation suggestions

1. Start with 10 to 20 processes that carry the highest risk of errors and are executed on a weekly basis.
2. Prepare separate test data and clear expected results for each process.
3. Use Aximo and Nexus respectively to evaluate the costs associated with autonomous execution and Playwright maintenance.
4. Statistics on actual defects found, false positives, false negatives, execution time, and manual interventions.
5. Based on stability, decide whether to retain AI agent testing, export the code, or use traditional approaches.
6. Before connecting to CI, set up retry mechanisms, isolation, screenshotting, logging, and manual review for failures.
7. Continuously remove duplicate tests and use Genesis to help identify coverage gaps.

Security and Quality Governance

• Test accounts must not reuse real administrator or customer accounts.
• Keys, verification codes, and tokens are managed using secure variables or credential management systems.
• The production environment only runs approved read-only or low-risk tests.
• Set clear boundaries for AI-driven clicking, as well as for the creation and deletion of data.
• Retain executed videos, screenshots, logs, models, and test versions.
• When personal information is involved, use masked data and establish retention and deletion policies.
• Evaluate AI test results in conjunction with unit, API, integration, and manual tests.

GitHub and open source

The Autify commercial testing platform, cloud execution environment, and AI agents are not fully open-source products. The official GitHub repository provides API documentation, CLI tools, JavaScript SDKs, CircleCI Orbs, example code snippets, and Webhook utilities.

Basic information

Recommendation score

The comprehensive recommendation score is 4.5 out of 5 points. The Autify product line offers a wide range of options, making it suitable for teams that wish to explore AI agents, Playwright, and no-code testing under one single vendor; however, it is necessary to carefully compare the overlapping features of the products, their individual prices, and the stability of AI-driven operations.

Frequently Asked Questions

What is Autify mainly used for?

It uses AI, natural language, low-code, and Playwright to help teams design, create, execute, and maintain software tests.

What is the difference between Aximo and Nexus?

Aximo is an application that is operated directly by AI, while Nexus creates editable and exportable tests based on Playwright.

Can Autify test mobile applications?

Yes, Aximo and Autify Mobile support iOS and Android; using Aximo in mobile mode requires more points.

Is there a free version of Aximo?

Yes, the free version provides 2,000 one-time credits that do not expire, and it supports testing on both web and mobile devices.

How much is the Nexus?

The Professional plan starts at $3,600 per year or $400 per month; additional fees may apply for users, workspaces, cloud concurrency, and AI services.

Will Genesis run tests automatically?

It is primarily responsible for generating and organizing test designs, while the actual execution can be carried out using Aximo, Nexus, or other tools.

What is AI self-healing?

After the interface elements change, the system attempts to identify the correct target based on other characteristics, thereby reducing the need for ongoing adjustment of the positioning.

Can the test code be exported?

The Nexus paid plan supports import and export using Playwright, and Aximo can also be used to generate scripts for various frameworks via MCP.

Does Autify provide APIs?

It offers public APIs, CLI, JavaScript SDKs, Webhooks, and an official integration with CircleCI.

Is Autify an open-source tool?

The core platform is not an open-source project, but the developers have made available a CLI, SDK, API documentation, as well as various integration projects.