Game Testing & QA Professional

Week by week

1. 1 – 2

   Foundations and the bug report

   What QA is for, how a studio is structured, severity and priority, and the anatomy of a report a developer can act on. You write your first reports this fortnight and get them sent back.

2. 3 – 4

   Functional testing and test design

   Reading a design document, deriving test cases, building a suite, and executing a structured pass. Boundary and edge-case thinking.

3. 5

   Compatibility and device matrices

   Building a representative device matrix, capturing logs that survive triage, and reporting bugs the developer cannot reproduce locally.

4. 6 – 7

   Regression and light automation

   Smoke suites, risk-based selection, and writing simple scripted checks that run against every build without you.

5. 8

   Performance and soak testing

   Measuring frame time, memory and thermals. Running an overnight soak and reading the graph that comes out of it.

6. 9

   Localisation and accessibility

   Pseudo-localisation, string length and concatenation failures, cultural review, and accessibility checks against published guidelines.

7. 10

   Multiplayer and network conditions

   Deliberately degrading a connection, reproducing desync, and capturing two clients at once so the report holds up.

8. 11

   Compliance and certification

   How platform requirement checklists work, why cert failures are expensive, and running an internal pass before submission.

9. 12

   Portfolio and getting hired

   Assembling your reports into a portfolio, the test exercises studios set at interview, and how QA applications are actually screened.