The use case: how Gameopedia deploys Harness
Gameopedia's QA team replaced Python-based Selenium UI test scripts with Harness AI Test Automation, using AI-assisted test creation and self-healing selectors to test a client-facing product. It also uses a dashboard to view test runs and tags to organize tests.
More reported results
Figures published in Harness’s case study. They are not independently measured by usedby.
Maintenance time cut by more than 40%
New engineers reached full productivity in 2-5 days compared to about 30 days with Selenium.
In the customer’s words
With Harness AI Test Automation, I would get back 2–3 hours daily, and I can use that time to be more productive and improve the tests for any edge case scenarios.Harness users in Gaming & Esports
Companies in the same sector, with public evidence.
See all Harness customersGo straight to the source
Based on Harness’s published case study. We check the public evidence; the results are reported by the vendor.
harness.io- Source published
- Nov 17, 2026
- Last checked
- Nov 22, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 2–3 hoursChecked
Printed word for word on the page, near the name of Gameopedia.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Gameopedia.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Gameopedia uses HarnessChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Maintenance time cut by more than 40%, saving each QA engineer 2–3 hours per day previously spent on script fixes.

