# How Gameopedia uses Harness

**40%**: “Maintenance time cut by more than 40%, saving each QA engineer 2–3 hours per day previously spent on script fixes.”

As published on [harness.io](https://www.harness.io/case-studies/gameopedia), October 2026. Captured by usedby on 2026-10-07.

- Company: [Gameopedia](https://www.usedby.ai/companies/gameopedia.md)
- Tool: [Harness](https://www.usedby.ai/tools/harness.md)
- Teams: QA

## What the story says

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 for test runs and tags to organize tests.

Summary written by usedby from the source page, in English. The figures are those of Harness and Gameopedia, not ours.

> Maintenance time cut by more than 40%, saving each QA engineer 2–3 hours per day previously spent on script fixes.

- **2-5 days**: “New engineers reached full productivity in 2-5 days compared to about 30 days with Selenium.”

> 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.
>
> Ajith KV, QA Engineering Lead

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 40% is printed word for word on the page, near the name of Gameopedia.
- Checked: the passage quoted above is copied word for word from the page, near the name of Gameopedia.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Gameopedia uses Harness. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/gameopedia-harness · How we check: https://www.usedby.ai/methodology