PLECK lesson 142 · suggested week 29, day 2
Write a final testable feature contract
Objective. Define what must work before release.
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.
Audience, originality, scope, acceptance and risks
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-L141.
Create ten required acceptance tests: launch, input, core rule, challenge, progress feedback, ending, replay, richer system, comfort/accessibility and source restoration. Each needs setup, action and expected result. Add two adversarial cases such as repeated rewards, insufficient resources, invalid save data or a boundary AI distance. Keep optional features in a separate list. These twelve tests establish the final minimum; changing them later requires a documented design revision rather than silently lowering expectations after a failure.
Worked example
A capstone risk experiment can test one readable chase/escape interaction before a designer builds several rooms around that mechanic.
Write a final testable feature contract — evidence task
- 1. Write ten required and two adversarial tests.
- 2. Assign evidence type and priority to each.
Deliverable. Final twelve-test contract.
Acceptance checks
- VGC-L142-T1. All twelve specify observable outcomes.
- VGC-L142-T2. The richer-system test covers a failure path as well as ordinary success.
Understanding question. Why distinguish a required test from an optional feature?
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 familiar 2D genre, a short complete loop and no networking. Reuse only code you can explain. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.
Optional extra. Propose one optional feature with an explicit dependency and a stop condition. 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.