
test my prototype systematically and write reproducible bug reports with severity ratings, use Godot’s debugging tools to find the cause of a bug, and keep versioned builds backed up on more than one storage device.
Instruction
Quality assurance (QA) is the discipline of finding problems before players do. It is a career in its own right: in Missouri, the U.S. Bureau of Labor Statistics estimated 2,930 jobs for software quality assurance analysts and testers in May 2025, with an annual mean wage of $93,990 (the national mean was $111,490; BLS Occupational Employment and Wage Statistics, May 2025). And every designer and programmer needs QA’s core skill: describing a problem so precisely that someone else can make it happen again.
Anatomy of a bug report.
- Title: short and specific. “Player falls through floor at right edge of Level 1” not “game broken”.
- Build: which version you tested (use a date or version number).
- Steps to reproduce: numbered, starting from launching the game. “1. Start Level 1. 2. Run right to the last platform. 3. Jump while holding right against the wall.”
- Expected result and actual result: “Player lands on platform” versus “Player passes through and falls off-screen; level does not restart.”
- Frequency: how often it happens when you follow the steps (for example, 4 of 5 attempts).
- Severity: how bad it is.
- Evidence: a screenshot or short screen recording.
Severity scale. Teams define their own, but a common four-level scale is: S1 Critical, a crash, lost progress, or anything that blocks finishing the game; S2 Major, a feature broken with a difficult workaround; S3 Minor, a problem with an easy workaround; S4 Cosmetic, a visual or text problem that does not affect play. Severity says how bad a bug is; priority, decided by the team, says how soon to fix it. A cosmetic typo in the game’s title can be high priority right before a showcase.
Functionality and usability. Report both, but label them. A functionality bug is when the software does not do what it should (the door does not open). A usability issue is when it does, but people struggle (nobody notices the door). Usability issues come mainly from playtests; functionality bugs come from systematic testing, such as trying every edge, every button and every state change.
Finding the cause in Godot. Once a bug is reproducible, the developer investigates:
- The Output panel shows your
print()messages and warnings. Printing a value at the moment something goes wrong (print("velocity: ", velocity)) often reveals the cause at once. - The Debugger panel lists errors with the script and line number. Click an error to jump to the line.
- Breakpoints: click beside a line number (or press F9) to pause the game when that line runs. You can then inspect every variable and step through the code one line at a time.
- Debug > Visible Collision Shapes shows every shape; many physics bugs are shapes in the wrong place.
- The Remote tab of the Scene dock shows the live scene tree while the game runs, so you can check whether a node exists and what its properties are right now.
The iteration log. Each entry records: date and build; what changed; why (the evidence, such as a playtest observation or a bug report); and what happened when you tested again. Over a project, the log becomes the story of your design decisions, and it is what reviewers, employers and your capstone reflection will draw on.
Versioned builds, storage and transfer. Every bug report names a build, so every build needs a name you can find again. Number builds major.minor.patch (0.3.1 becomes 0.3.2 after a fix and 0.4.0 after a new feature) and put the version and the date in the zip’s file name: mygame_v0.3.2_2026-11-10.zip. At the end of each session, close Godot, zip the project folder and record the build in your iteration log.
- Storage devices. Your computer’s internal drive (a solid-state drive or hard disk) is where you work; it is fast, but if the computer fails or is lost, everything on it goes too. A USB flash drive is cheap and portable but easy to lose, and it must be safely ejected before you unplug it, or the last file written can be damaged. An external drive holds many dated versions. An SD card behaves like a flash drive. Check a zip’s size in your file manager and the device’s free space before copying.
- A backup rule. A common rule of thumb is 3-2-1: three copies, on at least two kinds of storage, with one kept away from the computer, such as a drive kept in another room, or a cloud folder your family already uses, with a parent’s OK. Never create an account just to store a project. Keep the newest two backups; delete only the oldest.
- Transfer. To move a build to a tester’s laptop: copy (never move) the zip to a USB drive, eject it, copy it across and open it there; or use a shared folder on your home network, with a parent’s OK. Bluetooth is slow and suits one small zip, not a project folder of thousands of files. Never post a build on a public link. After any transfer, check that the copy opens and its size matches the original.
Each iteration-log entry ends with where that build’s backups are, so a broken build is never more than one session of lost work.
Professional tone. Bug reports describe the software, not the person. “Your code is bad” is never a bug report. Neutral, precise writing gets bugs fixed faster.
📖 Read for this lesson
The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
The game crashes every time the player pauses during the boss fight. What severity is this on the four-level scale?
Every tester walks past the key the level needs, although picking it up works perfectly. This is a…
Write one complete bug report on your own prototype, with title, build, numbered steps, expected and actual results, frequency and severity. The next day, try to reproduce the bug from your written steps alone, as if someone else had written them (or ask a family member to follow them). Revise any step that could not be followed.
Missouri standard: MM.FIL.5, MM.FIL.6
Your aunt will playtest build 0.3.2 on her laptop in another room, and you have a USB flash drive. Which plan moves the build safely and keeps it backed up?
How confident are you that you can write reproducible bug reports and use debugging tools to find a bug’s cause?
Practice
Work these on paper or in your notebook, then open Check your answer. Aim for all of Fluency and Application; try at least one Challenge.
Printable version: this unit’s practice workbook (PDF)
Fluency
Build speed and accuracy with the core skill.
- List the seven parts of a bug report from the lesson.
Check your answer
Answer: Title, build, steps to reproduce, expected and actual result, frequency, severity, evidence.Steps start from launching the game. - Give the four-level severity scale with one example of each.
Check your answer
Answer: S1 Critical: a crash, lost progress or anything that blocks finishing. S2 Major: a feature broken with a difficult workaround. S3 Minor: a problem with an easy workaround. S4 Cosmetic: a visual or text problem that does not affect play.Examples should match the definitions; teams define their own scales. - Name the Godot tool: (a) shows print() messages and warnings; (b) lists errors with script and line number; (c) pauses the game when a line runs; (d) shows the live scene tree while the game runs.
Check your answer
Answer: (a) Output panel; (b) Debugger panel; (c) a breakpoint (click beside the line number or press F9); (d) the Remote tab of the Scene dock.Visible Collision Shapes shows every collision shape.
Application
Use the skill in context. Show your reasoning.
- Rate each bug’s severity: (a) the pause menu’s title is misspelled; (b) the save point erases progress; (c) the door only opens if you walk away and back; (d) a moving platform sometimes carries you through a wall, but you can take a longer route around it.
Check your answer
Answer: (a) S4 Cosmetic; (b) S1 Critical; (c) S3 Minor (an easy workaround); (d) S2 Major or S3 Minor depending on how hard the longer route is; a strong answer explains the choice.Severity is how bad the effect is; priority is how soon the team fixes it, so a cosmetic typo can still be high priority before a showcase. - Rewrite this as a proper bug report title and steps: “Game broken on the bridge level, your code is bad.”
Check your answer
Answer: Model: Title: “Player falls through bridge plank 3 in Level 2.” Build: 0.3.2. Steps: 1. Start Level 2. 2. Walk right onto the bridge. 3. Stop on the third plank and jump. Expected: player lands on plank. Actual: player falls through and the level restarts. Frequency: 3 of 5.Describe the software, not the person, and give numbered steps from launch. - Functionality bug or usability issue? (a) the door does not open when you have the key; (b) nobody notices the key behind the crate; (c) the jump button does nothing after remapping; (d) testers cannot read the timer over the bright sky.
Check your answer
Answer: (a) functionality; (b) usability; (c) functionality; (d) usability.Functionality bugs: the software does not do what it should. Usability issues: it does, but people struggle. - Your build is 0.3.2. What number comes next after (a) a bug fix; (b) then a new feature? Write the zip name for the second one dated 2026-12-01.
Check your answer
Answer: (a) 0.3.3; (b) 0.4.0; mygame_v0.4.0_2026-12-01.zipmajor.minor.patch: a fix raises the patch number; a feature raises the minor number and resets the patch to 0. - In May 2025 the BLS estimated a mean wage of $93,990 for Missouri’s software quality assurance analysts and testers and $111,490 nationally. Find the difference and the Missouri mean as a percent of the national mean (one decimal place).
Check your answer
Answer: $17,500 lower; about 84.3%.111,490 − 93,990 = 17,500. 93,990 ÷ 111,490 ≈ 0.843.
Challenge
Stretch problems. Expect to think before you write.
- Your zipped project is 450 MB and your USB drive has 2,000 MB free. How many dated copies fit? Then describe a 3-2-1 backup plan for the project.
Check your answer
Answer: 4 copies (4 × 450 = 1,800 MB; a fifth would need 2,250 MB). Plan: three copies (the computer, the USB drive, and an external drive kept in another room or a family-approved cloud folder with a parent’s OK), on at least two kinds of storage, one away from the computer.2,000 ÷ 450 ≈ 4.4, so 4 whole copies. Keep the newest two backups and delete only the oldest; never create an account just to store a project.
Review
Keep earlier skills sharp.
- Review (Lesson 1.3): why should a bug report found during a playtest refer to “Tester B” rather than the tester’s name?
Check your answer
Answer: Privacy: collect only what you need and keep testers anonymous in notes and reports.Confidentiality works both ways: never share who said or did what.
Bug Report Template, Two Filled Reports and an Iteration-Log Entry
SLS original technique sheet; all reports are invented and illustrative · SLS original
Why this reading. The workshop asks for reproducible bug reports with severity, a bug fixed with its cause documented, and an iteration log. This reading gives the template, two filled reports (one functionality, one usability), the severity and priority table, a debugging trace and an iteration-log entry to copy. All examples are invented.
Bug report template
| Field | What goes there |
|---|---|
| Title | Short and specific |
| Build | Date or version tested |
| Steps to reproduce | Numbered, from launching the game |
| Expected / Actual | What should happen / what did |
| Frequency | Attempts that showed it, out of attempts |
| Severity | S1 to S4 |
| Evidence | Screenshot or short recording |
Filled report 1 (functionality; SLS original, invented)
| Title | Player falls through floor at right edge of Level 1 |
| Build | v0.3.1, 2026-10-05 |
| Steps | 1. Start Level 1. 2. Run right to the last platform. 3. Jump while holding right against the wall. |
| Expected | Player lands on the platform. |
| Actual | Player passes through and falls off-screen; the level does not restart. |
| Frequency | 4 of 5 attempts |
| Severity | S2 Major: the level can still be finished by jumping earlier, but the fall is hard to avoid. |
| Evidence | Screenshot with Visible Collision Shapes on |
Filled report 2 (usability)
Title: Key is not noticed. Steps: 1. Start Level 2. 2. Walk to the door without stopping. Expected: player collects the key first. Actual: 3 of 4 testers reached the locked door with no key. Frequency 3 of 4. Severity S3 Minor: pickup works, players miss it. Fix by design (lighting, placement), not code.
Severity and priority
| Level | Meaning |
|---|---|
| S1 Critical | Crash, lost progress, or blocks finishing |
| S2 Major | Feature broken; hard workaround |
| S3 Minor | Easy workaround |
| S4 Cosmetic | No effect on play |
Priority is the team’s decision. A typo in the title screen is S4 but may be top priority the night before a showcase.
Debugging trace for report 1 (illustrative)
- Reproduce: 4 of 5 attempts confirmed.
- Turn on Debug > Visible Collision Shapes: the last platform’s shape ends 16 px short of the tile edge.
- Add print(“pos: “, global_position) in the player: at the fall, x is 1,264, beyond the shape’s right end at 1,248.
- Cause: the collision shape was resized when the tile was copied. Fix: widen the shape by 16 px.
- Retest: 5 of 5 attempts land. Record it.
Iteration log entry
| Date and build | What changed | Why (evidence) | Result of retest |
|---|---|---|---|
| 2026-10-06, v0.3.2 | Widened last platform shape by 16 px | Bug report 1: 4 of 5 falls; shape 16 px short | 5 of 5 attempts land |