This section collects articles focused on game QA testing methods and workflows, including structured QA processes, bug reporting, evidence capture, test planning, and practical manual testing approaches used in real portfolio work. These articles show the repeatable QA methods behind my testing, making the work structured, consistent, evidence-led, and easier to communicate clearly to developers and teams.
A game QA testing article explaining why real bugs often appear when systems interact. Uses examples from Battletoads, Rebel Racing, and Shadow Point to show how input, UI, gameplay, and platform behaviour combine to create high-impact defects.
A practical guide to writing clear, reproducible QA bug reports using real examples. Covers structured reporting, repro rate, evidence, and how strong bug reports reduce friction between QA and development.
A practical game QA testing workflow showing how I capture gameplay footage, extract bug evidence, organise test data in Google Sheets, and create linked Jira bug reports across functional, exploratory, and regression testing.
A practical game QA functional testing workflow for a timeboxed QA pass, covering what to test first, how to prioritise risk, and what evidence to capture.
A practical game QA exploratory testing workflow on mobile, covering timeboxed sessions, test charters, controlled variation, interruptions, recovery, and the bugs scripted testing misses.
A practical game QA regression testing workflow showing how to turn patch notes into a targeted retest plan, prioritise risk, and make clear pass or fail decisions with supporting evidence.
All articles are written by Kelina Cowell as part of a personal QA portfolio. Content is original and intended to demonstrate practical QA knowledge and workflows.