Automate Game QA.

For most of the last year, the writing of game test cases in our studio took three hours a feature, give or take. A senior QA engineer would sit with a Confluence page — sometimes a PDF, if she was unlucky — and type out three hundred test cases by hand. She would then reread the spec, and do it all over again when something changed, which something always did.

Then, one afternoon in the spring of 2026, she handed the spec to a pipeline. A designer read it; an inspector reviewed the design; a writer filed the cases to Google Sheets. A first reviewer flagged problems, a fixer fixed them, a second reviewer went deeper, a second fixer went deeper still. Forty minutes later, three hundred test cases arrived — on par, she said, with what a smart three-year senior would have written. She had not touched her keyboard.