QArcade Reviews and Details

Questions & Answers

1. What makes QArcade unique?

   Most testing education is courses: you watch someone else find bugs. QArcade is practice. Each of its 15 short games trains one real testing skill by having you do it: spot the bug in a code snippet, triage a bug queue, review a bug report, plan a release by risk, diagnose a flaky test from its run log, write a CSS selector, test an API, find accessibility barriers, and catch an AI answer making things up. Every answer comes with an explanation, and a skill map shows where you're strong and what to practise next.

2. Why should a person choose QArcade over its competitors?

   Coding practice sites like Codewars and LeetCode train programming, not testing judgement. Course platforms like Udemy teach by video, which is easy to follow but hard to apply. QArcade sits in between: hands-on rounds that take a few minutes, on the skills testers are actually hired for, including newer ones like AI and RAG testing that few courses cover yet. You can play your first round without an account, and the free plan lets you play every day.

3. How would you describe the primary audience of QArcade?

   Software testers and QA engineers who want to sharpen their skills, manual testers moving into automation, people preparing for QA interviews, and developers who want to get better at testing their own code.

4. What's the story behind QArcade?

   I write a blog about test automation, and the question I kept running into was how testers actually get better. Most of the options are courses: you watch someone else find bugs, nod along, and then freeze when it's your turn. The skills that make a good tester, spotting what's wrong, judging how bad it is, deciding what's worth testing at all, only come from doing it, and there was nowhere to just practice.

   So in June 2026 I started building QArcade: short games where each round is a real testing task. You read code and find the planted bug, triage a queue of reports, review a teammate's bug report, plan a release in the hours you have, work out why a test flakes from its run log, and catch an AI answer that isn't backed by its source. Every answer comes with an explanation, because practice without feedback just repeats mistakes.

   The theme came naturally: we hunt bugs, so players climb 50 insect ranks, and the games are named after the things naturalists do in the field. Two rules shaped everything else. Nothing that gives you an advantage can ever be bought, only earned. And the games have to be worth playing for what they teach, not just for the points.

   I built it on my own, from the game content to the payments, and launched it on 31 October 2026, first to my blog's readers.

5. Which are the primary technologies used for building QArcade?

   TypeScript throughout. React with Vite and Tailwind CSS on the front end; NestJS with Prisma, PostgreSQL and Redis on the back end; BullMQ and isolated-vm for running player-written tests safely in the Mutation Arena; Stryker for mutation testing; Playwright and Vitest for its own test suite. Hosted on Hetzner with Coolify, payments by Paddle, error monitoring with Sentry.

6. Who are some of the biggest customers of QArcade?

   Individual testers and QA engineers (QArcade launched on 31 October 2026 and has no company customers yet)