PLECK lesson 77 · suggested week 16, day 2
Write acceptance before implementation
Objective. Translate a design promise into observable tests.
Godot Engine Standard desktop editor 4.7.2-stable, GDScript (Godot 4), Compatibility renderer. Headless Godot 4.7.2.stable.official.ed1daf0bf passed 106 assertions on the supplied scaffolds, including malformed JSON saves. Audio used the Dummy driver and a synthetic WAV, not a speaker. The visual editor, browser export, and signed-in submission were not tested. The desk still does not run a student's own upload.
About 55 minutes. The due date is chosen by a parent.
Scope, acceptance criteria, architecture and first playable integration
Suggested pace: Recall and predict 5 min; Read instruction and scaffold 12 min; Build or design the assigned artifact 25 min; Run acceptance tests 8 min; Explain and checkpoint 5 min.
Materials: Paper and pencil or a private text document, Local course folder and prior checkpoint, No paid assets or public account required.
Comes after VGC-L076.
An acceptance test describes setup, action and expected result. “Game works” is not testable enough. For a collector, a good test is “from a fresh round, collect the third item; completion appears once and movement stops.” Write tests for launch, core action, obstacle, progress, ending, restart and one accessibility feature. Include one boundary case such as a repeated goal event or insufficient inventory. These tests become the contract for your minimum game and keep optional ideas from moving the finish line.
Worked example
A minimum one-room collector can be described by one action, one obstacle, visible progress, one ending and restart. Extra rooms are optional until that loop works.
Write acceptance before implementation — evidence task
- 1. Write seven minimum acceptance tests and one boundary test.
- 2. Mark which artifact or log will demonstrate each.
Deliverable. Eight-test capstone contract.
Acceptance checks
- VGC-L077-T1. Every test names an observable result.
- VGC-L077-T2. At least one test checks a failure or repeated-event condition.
Understanding question. What is missing from “the player can collect items” as a full test?
Submit readable text or photos/scans of each numbered design page. Audio explanation may supplement a diagram or text, not replace requested artifacts.
If this is still shaky. Choose one earlier genre and one room. Keep one player action, one obstacle type and one goal until the loop works. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.
Optional extra. Propose an optional mechanic but do not build it before the minimum tests pass. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.
Turn in a typed answer, a JPEG, PNG, or WebP photo, a PDF scan, or an MP3, WAV, M4A, MP4, or WebM file up to 4 MB. A parent can log paper. One https address is stored as text and is not opened or run. Zip and code files are refused.
- Your first 2D game
Free public tutorial; no account; external asset download is optional, not used by this course.
· Opening this link does not submit the lesson.
This is a preview. A parent assigns the lesson and chooses the due date after the student is enrolled. The answer key is not on this page.