AutoTestX
Solutions and services

From your next release to your next upgrade, verified with AI.

AutoTestX is built for the moments teams re-test by hand. We bring the product and the people to get your first tests running, then your analysts take it from there. Running IBM Maximo? See the Maximo edition.

Solutions

Where teams start.

01 · Releases and deployments

Run your regression set after every deployment

Every release means the same manual checks, clicked through by people who have other work, or skipped when the deadline is close.

  • Group your regression cases into suites and run them in one go
  • Run after each deployment from GitHub, GitLab, Jenkins or Azure DevOps, or on a schedule
  • A release report separates new regressions from known failures
02 · Vendor updates and upgrades

A regression baseline before the next upgrade

Patches, fix packs and version upgrades to packaged applications (ERP, CRM, asset management) need a full regression pass, and the old spreadsheet rarely covers it.

  • Build tests on today’s version, run them again on the new one
  • Run history shows what passed before and what changed after
  • Self-healing proposes fixes for screens the upgrade moved
03 · Software built with AI

Verify what your AI coding assistant changed

Code gets written faster than anyone can re-test it by hand, and a page that loads can still break the business rule behind it.

  • Your assistant runs the suite through the AutoTestX MCP server and reads the evidence
  • Fail the pipeline when a suite fails, with a link to the run
  • Each failure classed: the application, the environment, the test data or the test
04 · Customizations and integrations

Check every change against the flows it touches

Configuration changes, new fields, scripts and integrations each carry a risk of breaking a flow nobody re-tested.

  • UI steps for lookups, tabs, frames and table rows found by business key
  • HTTP / API steps to create data, check it, or wait for an asynchronous job
  • The application’s own messages turned into checks
05 · Audit and change control

Evidence your change board can read

Proof of testing ends up as screenshots pasted into Word, assembled after the fact.

  • A report per run: every step, the data used, and a screenshot of each step
  • A plain-language view of every test for reviewers
  • Five roles per project and an audit trail; secrets redacted from logs and reports
06 · Data-heavy flows

One test, every row of your test data

Ten customer types, twenty products, fifty accounts: manual cycles test a few rows and hope for the rest.

  • Attach an Excel or CSV sheet: one run per row
  • Fetch data from an API request at run time
  • Pools of single-use records for data that can only be used once
Services

We don't hand you a tool and leave.

Every engagement starts on your own flows, with us building alongside your team.

$0 · no time limit

Free plan

Open to anyone: one authoring seat, one project and 100 AI generations a month, to automate your first tests on your own before you talk to anyone.

See pricing →
Included with a subscription

Guided onboarding

After the pilot, we help your team grow from ten cases to a regression suite of 25 or more, and settle who builds, runs and reviews tests.

See pricing →
Team and Business plans

Support

Email support on Team. On Business, priority support within 4 business hours and a quarterly review of your suite and results.

See pricing →
Business plan

Dedicated instance

AutoTestX on a server of its own, for your organization only, hosted on AWS in Canada or the US.

Talk to us →
Part of every engagement

Training for your team

Co-build sessions where your analysts record, edit and run tests themselves, so the suite never depends on us. Backed by the full documentation.

Read the docs →
How an engagement runs

Three weeks to ten tests you own.

  1. Week 0Agree success criteria, pass the IT pre-check, confirm the AutoTestX server can reach your test environment
  2. Week 1Kickoff, agent installed, the first three cases built with your team watching
  3. Week 2Your team builds cases four to six, with a weekly check-in
  4. Week 3Cases seven to ten, then a readout against the success criteria
  5. Weeks 4–8With a subscription: onboarding to 25 or more cases

What we bring

  • Kickoff, two co-build sessions and a weekly 30-minute check-in
  • The first three test cases built with your team
  • A response to blocking issues within one business day
  • A readout with evidence reports

What you bring

  • A named champion with about two hours a week
  • A test environment the AutoTestX server can reach, and test data
  • Ten test cases from your current manual set
  • Today’s numbers: time per case and cycles per year
For partners

Delivering upgrades and managed services?

On fixed-fee implementation and upgrade projects, for ERP, CRM or Maximo, regression testing is the part that is hardest to estimate. Consultancies and managed-service providers can use AutoTestX on their own client work, and offer automated regression as part of the service.

Talk to us about partnering →
Hosting and data

The short version for your IT team.

  • Hosted in CanadaAWS Canada (Central), or a dedicated instance in Canada or the US.
  • Test environments onlyAutoTestX runs against your test systems, not production.
  • No admin rightsThe Windows or Mac agent installs per user and makes one outbound HTTPS connection.
  • Secrets stay out of textStored per environment, never shown again, and redacted from logs and reports. Screenshots are not masked.

The full answers, including network reachability, data flow and deletion, are in the IT pre-check. Need a security questionnaire answered? Email info@autotestx.com.

Request a session

Tell us which change is coming next. We'll show you the tests for it.

In 30 minutes: a live demo of AI drafting, healing and explaining tests on a representative flow, and what your team would need for a pilot.