QA candidate 1-pager

What a mini test plan holds

• The objective of the test
• Scope, and what stays out
• Environment: device, OS, build and network
• The main risks
• Five to eight scenarios in priority order

Key question: with little time, what could damage the player experience the most?

Anatomy of a test case

1. Title — what will be verified
2. Precondition — the starting state you need
3. Steps — numbered, objective actions
4. Result — expected, actual, status and evidence

Example — “Restart the level after losing”. Lose the level, then tap Try again. Expected: the level restarts from the beginning and the controls respond.

Four possible statuses

• Passedexpected = actual
• Failedthere was a difference
• Blockedtesting was not possible
• Not runit has not been executed yet

Six lines make a great bug report

1. Title — [Area] + action + observed failure
2. Environment — device, OS, build and network
3. Precondition — the state before you start
4. Steps — a numbered sequence anyone can follow
5. Result — expected versus actual
6. Context — frequency, severity and evidence

Severity is the impact of the problem. Priority is how urgent it is to fix.

A 15-minute practice

• Open any simple mobile game.
• Write down the test objective, environment and three risks.
• List five scenarios in priority order and run three of them.
• Write one real or hypothetical bug report.

Bring your notes. You may use them during the exercise.

What we observe

Curiosity, clarity, attention to detail, prioritisation, the quality of your questions and your ability to explain decisions. You do not need to memorise terms or find many bugs.

CTFL is part of the journey — You do not need a CTFL certification to apply. At Kakunyn, interns study the CTFL syllabus as part of their development. The CTFL is required for conversion to a permanent role, and Kakunyn pays for the exam after the internal learning milestone is reached.