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
Customer story

How KitLegit tests every change

KitLegit is the AI authentication service for sports merchandise: collectors and marketplaces use it to check that a shirt is genuine, with a verdict in under 30 seconds. Their team ships fast, and GreatQA, their AI QA employee, tests every change to their dashboard and website.

KitLegit Tested on every change
The story

Every change checked, without slowing the team down

KitLegit's own AI does the authentication. That part is their expertise, and GreatQA never touches it. What we test is the product around it: the journeys collectors and sellers go through. On every change, GreatQA runs those end to end on a private copy: photos upload, the result page loads, the PDF certificate opens and shares, on desktop and phone screens.

2026 was a busy year for KitLegit, with Seller Certification growing and partnerships with Sporting Clube de Portugal and FanNFC, and every one of those launches touched the dashboard.

KitLegit
The numbers

June to October 2026

Taken from KitLegit's own systems on 24 October 2026.

441QA runs on real changes since June 2026 (227 tickets tested)
2,100test steps carried out, every one on a screenshot
350hours of hand testing saved, about 9 working weeks of a tester's time
512reports published, each with screenshots and a short video
Speed

Releases went from fortnightly to weekly

Testing used to be the thing a release waited on. With every change tested automatically, KitLegit ships the dashboard weekly instead of fortnightly, and a finished feature goes out when it is ready, not when there is time to test it.

Time between dashboard releases

Beforeevery 2 weeks
Nowevery week
Time

About 350 hours of testing, done automatically

Those 441 runs carried out about 2,100 test steps. Done by hand at around 10 minutes each to test and write up, that is about 350 hours, or 9 working weeks of a tester's time.

This is an estimate based on the number of test steps, not a measured figure.

Testing the same 441 changes

By handabout 350 hours
GreatQAdone automatically, no tester time
The setup

What their QA employee does

Every change tested

Each merge is picked up, tested on a private copy of the app with a fresh test account, and reported.

Phone and desktop screens

Collectors photograph their shirts from a phone. Every run tests the check flow and dashboard on desktop, tablet and phone screens.

Regression suites

64 test cases across the check flow, certificates, the seller dashboard and payments, run 318 times since July.

Want to hear it from KitLegit?

Book a demo and ask about KitLegit on the call. We'll show you real reports from their work, then run GreatQA on your own app.

  • Real reports from KitLegit's work
  • A live run on your own app
  • One clear price within two working days

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.