Write a useful test result
Capture reproduction, expected behavior and actual observations without secrets.
Use a separate record for each failed or blocked path. A screenshot alone rarely identifies which action failed. Private account identifiers can stay in the operator’s restricted notes; public reports should use labels such as Player A and Player B.
Step by step
Tick a step after observing the expected result. Saved on this device only.
01Identify the scenario
Record this guide’s path title, game runtime version, date/time, client/device and whether the environment used a real or explicit test clock.
A reviewer can locate the relevant scenario and distinguish player testing from an operator fixture.
02Describe prerequisites
List earned profession/character levels, relevant region, current activity, needed items and whether another tester participated.
Blocked progress is distinguishable from a command defect. Do not disclose private story choices beyond what the operator needs to reproduce.
03Write exact reproduction steps
Record the menu group, action name, chosen public recipe/work/route ID, quantity and sequence. Include the displayed job/order/round reference only in appropriate private notes.
Another tester can repeat the same intent without guessing what button was pressed.
04Compare expected and actual
Quote or paraphrase the relevant expected result here, then describe what actually appeared, including any error text and elapsed time.
Separate a rule mismatch from unclear wording, slow pacing, missing prerequisites or a personal preference.
05Attach sanitized evidence
Use a cropped screenshot or short screen recording showing the relevant UI. Remove passwords, link codes, cookies, bot tokens, signed URLs and another player’s private data.
The evidence remains useful without publishing credentials or player saves.
06State reproducibility and outcome
Mark Pass, Fail, Blocked, Not run or Design feedback. Note whether one retry with a fresh panel changed the outcome.
Do not call a path passed when only a form opened, a prerequisite was skipped or an operator injected its success.
Reference
| Field | Example format |
|---|---|
| Path | Barter, partial fill and stale quote |
| Environment | Runtime 0.4.3; Discord desktop; real clock |
| Prerequisites | A and B stationary in the same region; agreed test stock earned |
| Action sequence | Post quantity 2 → inspect quote → buy 1 → retry old quote |
| Expected / actual | Old quote should be refused / observed message and custody result |
| Outcome | Pass, Fail, Blocked, Not run or Design feedback |