| Author | Gaël MALVAR |
|---|---|
| Created | 11/17/2023 |
| Last Modified | 12/08/2023 |
📖 Table of content
This is the test plan for our version of Pac-Man coded in x86 assembly.
The purpose of these tests is to verify that the game works as expected and is playable. We'll detail how we'll test the game, what type of testing we'll do, and how we'll ensure the game works in the end.
| Term | Definition |
|---|---|
| Smoke test | A smoke test is a quick and basic check or test performed to verify that it works on a fundamental level. A smoke test ensures that the main functionalities of a program or system are operational without delving into detailed or exhaustive testing. |
| Functional test | Functional testing is a process categorized as black-box testing. It constructs test cases based on the specified requirements of the software component under examination. |
| Regression test | A regression test is a check to ensure that recent changes to a software application haven't negatively impacted its existing functionalities. It helps catch unintended side effects or "regressions" that might occur when new features or updates are added. |
| Unit test | A unit test is a specific kind of testing conducted by developers on isolated components (units) of a software program. Developers create and execute unit tests to verify the correctness of individual functions or methods within the code. |
| Test case | A "test case" is a specific set of instructions or conditions that are designed to determine whether a software application, system, or component functions correctly under certain circumstances. It's a detailed scenario or situation used to verify that the software behaves as expected. |
The strategy that will be used to test the game is to test it manually. The tester will have to test the game throughout the development phase and also afterwards in order to prevent the appearance of bugs and to be able to resolve them if there are any.
First, we'll run a smoke test to see if the basic functionality works. When the smoke test is successful, we will then perform a functional test to ensure all features work as expected. Then we will do a regression test after each new version to see if any new bugs appear.
This is a short description of the somke test we will perform
- Start the game
- Exit the game
- Movements
- Collision
The purpose of these tests is to verify and confirm that the main features of our game work well.
| Name of the test | Description |
|---|---|
| Maze Navigation | Verify that the player can navigate the maze, be able to use the tunnels, consume pellets, and escape from enemies. |
| Foes Behavior | Ensure that the behavior of the foes works as expected for each of them. |
| Game Levels | Check if the game progresses through levels correctly. The game should change level when the player eats all the dots. |
| Win | The game should end when the player wins all levels. |
| Lose | The game should end when the player loses all lives. |
| Live | The number of lives should decrease when the player is eaten. |
| Score | The score should increase when the player eats a dot, a pellet, or an enemy. |
| Test | Description |
|---|---|
| Cross-platform compatibility | Test the game on various platforms and devices and ensure that the game is responsive. |
| Peripheral devices | Test the game with different peripherals such as keyboards and controllers. |
| Test | Description |
|---|---|
| Movement and Controls | Test the responsiveness and accuracy of player movement controls. |
| Load Testing | Evaluate the time it takes for the game to initially load as well as the loading time between levels to ensure a smooth experience. |
| Stress Testing | Push the game to its limits to identify any breaking points, such as excessive collisions or power-ups. |
This section is dedicated to the progress of the testing phase, including smoke tests, functionality tests and bug reports. The game will be tested throughout development and after each new version.
- Project timeline :
Start of the project : 11/06/2023
Project deadline : 12/21/2023
| Task | Start date | End date |
|---|---|---|
| Report bugs | 11/27/2023 | 12/21/2023 |
| Unit test | 11/27/2023 | 12/21/2023 |
| Smoke testing | 12/04/2023 | 12/04/2023 |
| Production of documents | 11/17/2023 | 12/08/2023 |
| Start of the test on the working prototype | 12/11/2023 | 12/11/2023 |
| Functionality test | 12/14/2023 | 12/15/2023 |
| Regression test after each new version | 12/14/2023 | 12/21/2023 |
During the testing phase, all the tests carried out will be stored in the " TestCases.md" file.
Here is an example of a test case :
| Test Case ID | 1 |
|---|---|
| Name | Name of the test |
| Description | Description of what should happen |
| Pre-conditions | What conditions must be met before starting the test |
| Steps | Step taken to obtain the expected result |
| Expected Result | Expected result after the test |
| Actual Result | Actual result after test |
| Status | Test status (To test, In testing, Tested) |
| Priority | The priority of the test (High, Medium, Low) |
In order to test the game, we will use several tools.
We will run and test the game on different machines, we have 3 at our disposal, 2 of the machines were provided by the school: the Lenovo and the MacBook, the 3rd was provided by a member of our team.
Lenovo ThinkBook :
- ThinkBook 14 G4 IAP
- Processor : 12th Gen Intel® Core® i7-1255U 1.70 GHz
- RAM : 16.0 GB
- System : 64-bit operating system, x64-based processor
- Operating system : Windows 11 Pro ( Version : 22H2 )
MacBook Air :
- MacBook Air 13″
- Processor : Apple M1 chip
- RAM : 8.0 GB
- Operating system : macOS Ventura
Desktop computer :
- HP compaq 500b mt
- Processor : Intel® Pentium® E5400 2,7 GHz
- RAM : 2 Go DDR3
- Operating system : Windows XP SP3
We will use different software to run the game, test it, report different bugs and resolve them.
- DOSBox to run the game and test it on our different Hardware.
- DOSBox 0.74-3 for Windows
- DOSBox 0.74-3 for macOS
- NASM to compile the assembly language.
- GitHub to report bugs.
- Visual Studio Code ( version 1.84.2 ) to develop the game and fix bugs.
Issue n°X
Date
MM/DD/YYYY
Description :
Actions performed :
Actions performed to reproduce the bug
Expected result :
What should happen when the program works as expected
Actual result :
What actually happened
Screenshot :
(if it gives additional informations)