Sample QA report
This is what you get from a Jumbo Jelly test pass: a summary with the top 3 risks, severity on 4 levels, priority on 4 levels, and bug entries your programmers can act on without a follow-up question. The same format comes with a Smoke Test and a Launch Health Check.
Example only. “Example Game” is a fictional game made up to show our reporting format. It is not a real project, studio or client, and all bugs, numbers and builds are illustrative.
1. Summary
Overall: The core loop is stable on mid- and high-range PCs. Two issues should be fixed before Early Access: a save corruption on quit and a progression blocker in Chapter 2. Performance on low-end hardware is the biggest remaining risk.
| Severity | Count |
|---|---|
| Critical | 2 |
| Major | 5 |
| Minor | 11 |
| Cosmetic | 7 |
| Total | 25 |
Top 3 risks before launch
- EG-014 Save file corrupted when quitting during autosave (Critical): players lose progress, a classic review-killer.
- EG-021 Bridge lever in Chapter 2 does not respond after reloading a save (Critical): blocks progression.
- EG-030 FPS drops to ~18 in the Market area on a low-end PC (Major): below your minimum spec target.
Coverage: Chapters 1–3 critical path, settings menu, save/load, controller (Xbox pad), keyboard rebinding, 3 hardware tiers. Not covered: Chapter 4 (not in build), multiplayer (out of scope).
2. Severity and priority
We rate every bug on two separate scales. Severity is how bad it is for the player. Priority is how soon we suggest fixing it, given your milestone. We switch to your own labels if you have them.
Severity
| Level | Definition | Example |
|---|---|---|
| Critical | Crash, freeze, progression blocker, save or data loss, or a bug that makes the game unplayable for a group of players. | Game crashes when opening the map. |
| Major | A feature is broken or a serious issue affects many players, but there is a workaround. Includes big performance drops. | Controller cannot navigate the inventory; mouse works. |
| Minor | Something works, but not as intended. Players notice, but can carry on. | Wrong item count shown after crafting. |
| Cosmetic | Visual, audio or text polish. | Texture flickers on a distant wall; typo in a tooltip. |
Priority
| Level | Definition |
|---|---|
| P1: Fix before release | Must be fixed before the milestone build goes to players. |
| P2: Fix soon | Should be fixed before or shortly after release (first patch). |
| P3: Fix when possible | Nice to fix; low player impact. |
| P4: Backlog / decide | Design question or edge case; the studio decides. |
3. Bug report fields
| Field | What goes in it |
|---|---|
| ID | Tracker ID (e.g. EG-014) |
| Title | What happens + where + when. Readable without opening the ticket. |
| Severity / Priority | See the scales above |
| Build / Branch | Exact version and Steam build ID |
| Area | Level, menu or system |
| Hardware / OS | CPU, GPU, RAM, OS, input device, resolution |
| Reproducibility | e.g. 5/5, 3/5, 1/10 (how many times out of how many attempts) |
| Preconditions | Save file, settings or state needed before step 1 |
| Steps to reproduce | Numbered, one action per step |
| Expected result | What should happen |
| Actual result | What happens |
| Attachments | Video (with timestamp), screenshots, logs, crash dump, save file |
| Notes | Workarounds, related bugs, what we already ruled out, a hunch about the cause (labeled as a hunch) |
4. Example entries
EG-014 · Save file corrupted when quitting to desktop during autosave
| Severity / Priority | Critical / P1: Fix before release |
|---|---|
| Build | 0.9.4 (build ID 1234567) |
| Area | Save system / Pause menu |
| Hardware | Mid tier: Ryzen 5 3600, GTX 1660 Super, 16 GB RAM, Windows 11, Xbox controller, 1080p |
| Reproducibility | 4/5 |
Preconditions: Any save past the Chapter 1 checkpoint.
Steps to reproduce
- Load a save in Chapter 1, after the “Old Mill” checkpoint.
- Walk through the mill door to trigger the autosave (spinning icon, bottom right).
- While the icon is visible, open the pause menu and choose Quit to Desktop.
- Relaunch the game and choose Continue.
Expected result: The game loads the last completed save.
Actual result: “Save data corrupted” message. The save slot is empty; the backup slot is also overwritten.
Attachments: EG-014_repro.mp4 (issue at 0:42), output_log.txt, corrupted save file slot1.sav
Notes: Does not happen if you wait for the autosave icon to disappear. Quitting from the main menu during autosave is not possible, so this only affects the pause menu path. Possible cause (hunch): quit is not waiting for the save write to finish.
EG-021 · Bridge lever in Chapter 2 does not respond after reloading a save
| Severity / Priority | Critical / P1: Fix before release |
|---|---|
| Build | 0.9.4 |
| Area | Chapter 2, “Canal” area |
| Hardware | High tier: i7-12700K, RTX 3070, 32 GB RAM, Windows 11, keyboard + mouse, 1440p |
| Reproducibility | 5/5 |
Preconditions: Save file EG-021_before_bridge.sav (attached).
- Load the attached save.
- Pull the bridge lever (interact prompt appears, animation plays).
- Before the bridge finishes lowering, open the pause menu and Load Last Checkpoint.
- Walk back to the lever and press interact.
Expected result: The lever can be pulled again and the bridge lowers.
Actual result: The interact prompt shows, but nothing happens. The bridge stays up and the player cannot continue. Only a full restart of the chapter fixes it.
Attachments: EG-021_repro.mp4 (0:15–0:58), save file
Notes: Lever state seems to stay “used” after reload while the bridge state resets. The same pattern may apply to the gate lever in Chapter 3 (checked once, could not reproduce yet; we will keep an eye on it).
EG-030 · FPS drops to ~18 in the Market area on a low-end PC
| Severity / Priority | Major / P2: Fix soon |
|---|---|
| Build | 0.9.4 |
| Area | Chapter 1, Market |
| Hardware | Low tier (your minimum spec): i5-6500, GTX 1050 Ti, 8 GB RAM, Windows 10, 1080p, Low preset |
| Reproducibility | 5/5 |
- Set graphics preset to Low, resolution 1080p.
- Enter the Market area from the north gate.
- Turn the camera toward the fountain while the crowd is visible.
Expected result: Stable 30+ FPS on minimum spec (per your Steam page).
Actual result: FPS drops to 16–20 for as long as the fountain and crowd are on screen. Other areas run at 35–50 FPS on the same settings.
Attachments: EG-030_fps_capture.mp4 with FPS overlay, settings screenshot
Notes: Turning off “Crowd density” in Advanced settings brings it back to ~32 FPS. Mid and high tier PCs are fine (55+ and 100+ FPS).
EG-047 · Controller cannot select the “Sell” tab in the shop
Severity / Priority: Major / P2 · Area: Shop UI · Hardware: Mid tier, Xbox controller · Reproducibility: 5/5
Steps: 1. Open any shop. 2. Press RB to switch tabs.
Expected: Focus moves from “Buy” to “Sell”.
Actual: Focus stays on “Buy”. “Sell” is only reachable with the mouse. Controller-only players cannot sell items.
Attachments: EG-047.mp4
EG-063 · Tooltip text overflows its box in French
Severity / Priority: Cosmetic / P3 · Area: Inventory, French language · Reproducibility: 5/5
Steps: 1. Set language to French. 2. Hover over the “Rusty Key” item.
Expected: Full description inside the tooltip.
Actual: Last line runs outside the box and is cut off.
Suggested fix (from our native French tester): shorten “Une vieille clé rouillée qui ouvre peut-être quelque chose” to “Une vieille clé rouillée. Elle ouvre sûrement quelque chose.”
Attachments: screenshot
5. Game-feel notes (optional)
Short observations from playing like a player. Not bugs; the studio decides.
- Camera: In tight corridors in Chapter 2 the camera clips into walls often enough to be disorienting. A slightly closer default distance indoors might help.
- Difficulty spike: The Chapter 2 boss took both testers 8–10 attempts, compared with 1–3 for earlier fights. Might be intended; worth a look before Early Access reviews.
- Onboarding: The dodge mechanic is introduced only through a loading-screen tip. Both testers missed it until the boss fight.
6. Next steps
- Fix P1 bugs (EG-014, EG-021); we verify them on the next build.
- Regression pass on save/load once EG-014 is fixed.
- Re-check EG-030 after any performance changes, on all 3 hardware tiers.