Product

From the first page to the release decision.

Seven modules, in the order you work: capture the application, write what it must do, build the tests, run them, read the result, keep the tests healthy, and measure what they prove.

01 / Discover

Teach it your application.

SmartestQA scans your application and remembers it: every page, every control, and how the pages connect. Everything after this builds on that map.

  • Web, mobile and desktop applications.
  • Every control becomes a reusable building block, captured once.
  • Your business rules sit next to the map, so the AI tests what matters.

More in the docs

Discover
LoginCartCheckout
Controls capturedMap ready
  1. scanEvery page and every control, captured oncesaved
  2. mapHow the pages connectApp Map
  3. rulesYour business rules, next to the map
Illustration. Page names are examples.

02 / Analyze

Write down what it must do.

Requirements live next to the tests that prove them. Write them yourself, or let AI draft them from your documents.

  • A spec or a user story becomes requirements and test cases.
  • AI scores each requirement and shows what is missing.
  • Every rule is linked to the tests that prove it.

More in the docs

Analyze
Checkout
Pay with a saved cardprovenCard is declinedprovenCampaign codeno test yet
Linking tests to rulesOne gap, in plain sight
  1. linkedEvery rule points at the tests that prove ittraceable
  2. aiDrafted from your documents, scored for gaps
  3. gapWhat has no test is in plain sightno test yet
Illustration. Requirement names are examples.

03 / Automate

Build the tests.

Record a flow once, or describe it and let AI write the steps. One test can cross the browser, the API, the database and the inbox.

  • No code to write or maintain.
  • One test, many data rows.
  • Try a test at once, before you schedule it.

More in the docs   Record and replay

Automate
REC
Sign inOrder confirmed
1  Type the e-mail2  Click Sign in3  Check the orderSaved as a test
  1. recDo the flow once, the steps write themselves
  2. proofA check at the end, so green means it worksproof
  3. tryRun it at once, before you schedule itPassed
Illustration. Step names are examples.

04 / Schedule

Turn tests into runs.

A pipeline runs your tests when you want them: now, every night, or on every deploy from CI/CD.

  • On our servers, inside your network, or on real devices.
  • Log in once before the tests, clean up after them, always.
  • Every run leaves a report.

More in the docs   Build a regression suite

Schedule
MonTueWedThuFriSatSun
Every night, 02:00Thursday failed: task openedFixed by Friday
  1. whenNow, every night, or on every deployscheduled
  2. whereOur servers, your network, or real devices
  3. orderLog in once before, clean up always after
Illustration.

05 / Report

Read what happened, and why.

Every run becomes a report you can read in a minute: what passed, what failed, where and why.

  • Every step with its screenshot, video and log.
  • AI tells a real bug from a test problem from a flaky run.
  • Share it as PDF, or open a task from the failure.

More in the docs

Report
Log inAdd a noteEdit a noteDelete the note
AI verdict: Real BugScreenshot, video and logTask opened
  1. whereThe step that broke, firstFailed
  2. whyReal bug, test problem or flaky runAI verdict
  3. proofScreenshot, video and log for every step
Illustration. Test names are examples.

06 / Maintain

Keep the tests honest.

When your application changes, the tests adapt, and a person stays in charge.

  • Auto-heal repairs a moved control, and refuses when the application itself is broken.
  • Every repair waits for your approval.
  • Browser traffic from your runs turns into API tests.

More in the docs   Network Calls to API tests

Maintain
PayPay
#submit-btn[data-testid="pay"]Same result as beforeApproveReject
  1. healA moved control is found againrepaired
  2. stopA broken application is never hiddenfails
  3. youEvery repair waits for your decisionreview
Illustration. The locators are examples.

07 / InSight

Know what your tests really prove.

One dashboard for two questions: how did the runs go, and how much of the application is really proven?

  • Success rate, flaky tests and time saved, for any period.
  • Coverage of requirements and risk, counted only from tests that check a result.
  • The next things to fix, ranked.

More in the docs   Prove every requirement is tested

InSight
Test
Health
Requirement coverageRisk coverageScenario coverageAction coverageFix these first
  1. truthCoverage counted only from tests that check a result
  2. nextThe next things to fix, ranked
  3. runsSuccess rate, flaky tests and time saved
Illustration. The lengths are examples.