Product
Tests every changeRegression suitesReportsNarrated videosPhone and tablet screensHow it worksIntegrationsTest environmentsSelf-growing automationsScreen recordingChangelog clipsYour AI provider
Use cases
Engineering teamsQA teamsProduct managersMarketing and supportStartupsScale-upsEnterprise
Customers
GreatLabKitLegitAll customersFounding customers
Pricing
Resources
DocumentationQuick startCommand lineWriting regression testsSupportAbout usFounding customersContactCareers
Book a demo Try for free
Reports

A report anyone on the team can read

After every run, your AI QA employee writes up what it tested: every step with a screenshot, the evidence behind each finding and the test data it created. The report is filed in your docs, linked on the ticket and summed up in your team chat.

A QA report marked Found a problem, with numbered steps on screenshots, the evidence, and the file and line in the code
What is in a report

Written for product people, detailed enough for developers

The result and a summary

Works as described, Found a problem, or Blocked with the reason. Plus the AI model that ran it and a short summary of what was tested.

Every step, on screenshot

Numbered steps with a screenshot for each one, so you can follow the test without running it.

Evidence

Console messages, network calls, and request and response bodies for anything that went wrong.

Findings

Expected against actual for every problem, with the file and line in your code where it comes from.

Test data created

A list of the accounts and records the run created, so nothing is a mystery later.

The test script

The exact script that was run, so a developer can run the same test again.

Your docs

Filed in a tidy page tree

Reports are published to Confluence in a structure that stays easy to browse: one section per area of your app, one page per ticket, and one sub page per run. The video sits at the top, the screenshots are attached.

  • One off runs get their own section
  • Deep link straight to the video
QA reports filed as a page tree in the docs: one section per area, one page per ticket, one page per run
Your tickets and test plan

Proof on the ticket, history in your test manager

The report, the video and the test run links are written onto the Jira ticket. Results, screenshots and one defect per finding are pushed to Qase, so your test history builds up on its own.

  • Three evidence links on every ticket
  • Test cases created or reused automatically
  • Defects linked back to the ticket
A ticket with the QA panel: Found a problem, the report, the video and a Test this ticket button
Your team chat

One short message per run

A Slack message with the ticket, the result and links to the full report. When it found a problem or was blocked, the video is attached and the people who made the change are mentioned. When the change works as described, they are only copied in.

  • No noise while a run is waiting or paused
  • Runs that could not start are reported too
A team chat message with the result, the people who made the change mentioned, and links to the report and video

You build the product.
Your QA employee checks it.

Show us your app. We'll run GreatQA on a real change of yours, live on the call.