Skip to lesson
LESSON 42 / 44 · Intermediate

Test and debug a complete game

Use small repeatable checks before sharing an adventure.

Open editor in a new tab ↗

Before you begin

Export a backup and write the intended start, goal and failure conditions.

Build it step by step

  1. Play from a fresh start. Test movement, jumping, crouching beneath a ceiling, collisions and any special actions independently.

  2. Check each rule with a simple example. Remove duplicate rules that award score or damage twice; review once-only versus continuous execution.

  3. Test enemies, projectiles and animations together. Check that copies expire and loops do not keep spawning unlimited objects.

  4. Cross every screen boundary and level exit. Test checkpoints, restart and the configured progress carry-over.

  5. Repeat on desktop keyboard and a real touch device. Pause, change focus, resume and release controls. Verify sounds and readable instructions.

  6. For saved adventure progress, save, refresh and continue in the same browser. Separately reopen the editable project to verify creator saving.

TRY THIS IDEA

Practical example

A test sheet records: collect one coin +10; take one hit −1; cross two screens; reach checkpoint; refresh and continue.

Test your work

Each test has an observed result rather than an assumption based on the editor preview.

If it does not work

If motion stutters, compare a simpler scene and reduce simultaneous effects or copies. A screenshot alone cannot establish the cause of a runtime problem.

MAKE IT YOUR OWN

Student challenge

Give your game to someone who has not seen it and record three confusing moments.

Show the result to a partner. Explain what you changed and how you tested it.

Keep exploring