Every ticket starts the same way. Read the user story, think through the edge cases, work out what the change touches elsewhere, write the cases out. On anything non-trivial that is close to an hour of work, and it happens before a single test has been executed.

Then the suite has to be run by hand. Open the case, read step one, go do it, come back, read step two, with the engineer present for all of it. Anything that fails gets written up as a bug, which is a second pass over work already done once. It is careful, necessary work. Almost none of it is creative, and it takes most of the week.

What we built

QA flow runs the front half of the ticket. It reads whatever spec exists, writes the cases a QA engineer would write, runs them unattended, and files what breaks. Three things stay with the engineer: approving the suite, adding the edge cases only they would think of, and fixing the bug. Everything between those decisions happens without anyone watching.

Three stages of manual work come off the ticket, and the three decisions worth making stay. What comes back is about twenty two hours a week per engineer, spent on testing that never fit before.




Want this pipeline running on your backlog? Get in touch.