Chapters
Prod [8/12]
Test Plan
0 0
0

[GameJam daily schedule]

Day 3

1pm. Dev master class - by invitation only
7pm. Sponsor diner

Jessica, our freelance tester, is meeting the team.
As preparation work, she studied our feature list. She also played our latest version.
She is now building a TEST PLAN.

Not an easy task. Let's help her.

A TEST PLAN is a strategic document detailing the following themes: Tests objectives | Tests scope | Tests schedule
Drag at least 7 test plan elements (grey boxes) to the correct theme box, then submit.
No mistake wins a bonus star

TEST PLAN / THEMES

🏆
Objectives

📋
Scope

🗓️
Schedule

Find all critical bugs that affect the player's experience

Aliens: Behavior, movements, spawning logic, & collision detection.

Alpha testing part 1: aliens & player ship, in 2h

Player Ship: controls, shooting, & hit detection.

Alpha testing part 2: gameplay & feedback, in 2 hours

Make sure the game is playable on target browsers

Beta testing part 1: gameplay and UI/UX, in 2h

Check that the user interface & visuals are intuitive and functional.

Gameplay: Difficulty, win/lose conditions, & scoring system.

Ensure the game mechanics function well & respond as intended.

Beta testing part 2: graphics & performance, in 2h

UI/UX: Layout & screens. Immersion, graphics and tone.

Good answers: 0

When your test plan is done, please Submit:

Additionally, here are 4 critical steps to build a good test report:

1. Define test scope

Version name & date Scope open for testing Platform and specs Language

2. Define test objectives

Functional testing Performance testing Usability testing Target test coverage

3. Determine test deliverables

Define bugs priorities Write test cases Test report: fail / pass Bugs descriptions Logs & reproduction steps

4. Design test strategy

Manual testing vs Automatic tests Enabling user data log Test risks

✅ Jessica finalized the Test Cases:

ALIENS	PLAYER SHIP	GAMEPLAY	UI/UX
TC1: Verify aliens move horizontally and drop down as expected.	TC6: Check left and right movement responds to player input.	TC11: Confirm game-over conditions trigger when all shields are used.	TC16: Verify that the score is displayed correctly and increases when an alien is hit.
TC2: Check that aliens fire projectiles at regular intervals.	TC7: Verify that the player ship can shoot projectiles.	TC12: Verify the win condition when all aliens are defeated.	TC17: Ensure the game-over screen appears when the player loses.
TC3: Confirm collision detection when aliens are hit by the player’s shots.	TC8: Confirm that the player ship’s projectile collision works with aliens.	TC13: Check that a Ship and Alien collision triggers an explosion and a game over.	TC18: Check the countdown and encounter with SpaceTron when the game loads.
TC4: Ensure aliens speed going down increases after several waves.	TC9: Ensure the player ship loses a shield when hit by an alien projectile.	TC14: Ensure the game difficulty is balanced and challenging.	TC19: Confirm the game performance stability (framerate) and that controls are responsive.
TC5: Verify aliens spawn properly when a new wave starts.	TC10: Verify the player ship respawns correctly after losing a shield.	TC15: Verify that the game can restart after a game over.	TC20: Verify starfield background.

🗓️ Test Schedule for 4 Sessions (2 hours each)

SESSION	FOCUS AREA	SCOPE	TEST CASES
1. Wednesday 2pm 2 hours Alpha build	Aliens & Player Ship: Ensure core functionalities are working properly. Identify critical gameplay bugs related to movement and shooting.	Aliens: Movement, shooting, and behavior patterns. Player Ship: Controls, shooting, and collision detection.	Aliens: TC1-TC3 Player Ship: TC6-TC8
2. Wednesday 4pm 2 hours Alpha build	Player Ship & Gameplay: Ensure gameplay mechanics and player ship interactions are solid. Verify the player ship's functionality and core gameplay mechanics.	Player Ship: Additional tests for hit detection and respawning. Gameplay: Win/lose conditions and difficulty progression.	Player Ship: TC9-TC10 Gameplay: TC11-TC13
3. Thursday 2pm 2 hours Beta build	UI/UX Elements: Check user interface components for functionality and clarity. Ensure the interface, score display, game-over screens and Restart button work as intended.	UI/UX, layout, game-over screen, and responsiveness.	UX: TC16-TC19
4. Thursday 4pm 2 hours Beta build	Immersion & final checks: Ensure overall game experience and visuals are immersive. Verify visual and effects enhance immersion.	Immersion: Graphics, effects, and general game atmosphere. Final verification of any remaining test cases.	Gameplay: TC14-TC15 UI/UX: TC20

Congratulations!

Level 1

200

400

600

800

After a few minor fixes, Luke compiles version V0.2, our Alpha candidate.
The Alpha build is missing a few features:
[DIFFICULTY TUNING], [ALIEN VISUALS], [MEET SPACETRON], [CONTEXT & TONE]
The team accepts to develop them after Alpha as these features do not require code.

Production / Mission [8/12] completed done

Our closing phase, Thursday and Friday morning, is going to be tight...

After lunch, the team attends the dev MasterClass.
Jessica is ready to test the Alpha version.
The playtest is about to start...

Headers

[GameJam daily schedule]