Game tester

Game testing reportswritten from my own playthroughs

I test games from the player's side, then write the findings up in a structured way so the development team can act on them straight away. Pick a game card below to open that game's report list.

Games tested
1
Reports
2
Storage
Notion

Games I have tested

Click any card to open that game's list of reports.

Game2 reports

Age of Crowns

A game I test from the player's side: walking the play flow from the start to a battle session, hunting for behaviour that deviates from what should happen, then writing reports the development team can act on straight away.

  • Walking the main flow from the start to the first battle
  • Hunting for behaviour that breaks the rules of the game
  • Rechecking older findings after a fix ships
See the reports→

How I test

  1. 01

    Hunting for behaviour that deviates

    I walk through the play flow the way an ordinary player would, then pay attention to the parts that do not match the rules of the game or what should have happened.

  2. 02

    Writing reproduction steps

    Every finding comes with steps someone else can follow to bring up the same problem, not just the conclusion at the end.

  3. 03

    Attaching evidence

    Screenshots and recordings prove the finding really happened, so the development team never has to guess what I saw.

  4. 04

    Rating the severity

    Findings are ordered by how much they hurt the play experience, so the most disruptive work can be handled first.

The full reports live in Notion. If a link asks for access, email me and I will open it for you.