Skip to content

bucsspring2024/final-project-bestteam-p

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

68 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Open in Visual Studio Code

⚠️ Everything between << >> needs to be replaced (remove << >> after replacing)

CS110 Final Project Spring 2024

ESCAPE

Team Members

Emily Goldstein


Project Description

My project is a simple dungeon-crawler style game with a dog character trying to get to the exit. It implements the arrow keys and has ghosts that will kill the dog if it touches them.


GUI Design

Initial Design

initial gui The user would use their mouse to select different choices displayed on screen. The screen would also show the outcome of their choices.

Final Design

final gui The user would use their arrow keys to direct the dog throught the maze and around the ghosts. The end goal is clear, shown by the door, and the enemies consistantly move on the screen. The menu and instructions screen are clear too, with clickable buttons that lead the user to actual gameplay.

Program Design

Features

  1. start menu
  2. moveable character
  3. moving enemies
  4. wall barriers
  5. final outcome screen

Classes

  • Maze: Maps out and draws the maze for the player to travel through. It also check if a cell acts as a wall inside.
  • Door: Draws the door object that acts as an exit when the player collides with it.
  • Dog: Draws and establishes the movement of the game's protagonist.
  • Ghost: Draws and establishes the movement of the ghosts which can kill the protagonist.

ATP

MY COMPUTER DID NOT SHOW THE ATP AS A TABULAR FASHION, ONLY AS AN OFFSET TABLE TYPE THING THAT WAS VERY DIFFICULT TO TYPE IN

Test Case 1: Menu Screen Functionality -Test Description: Verify that the main menu buttons work. -Test Steps: 1. Start the game. 2. Press the "Start" button. 3. Verify the game starts when the button is pressed. 4. Press the "x" button. 5. Verify the game exits when the button is pressed. -Expected Outcome: The menu displays all necessary buttons, and the necessary buttons work as intended.

Test Case 2: Mouse Movement -Test Description: Verify that the mouse moves left, right, up, and down with appropriate arrow keys. -Test Steps: 1. Start the game. 2. Press the left arrow key. 3. Verify the mouse moves left. 4. Press the right arrow key. 5. Verify the mouse moves right. 6. Press the up arrow key. 7. Verify the mouse moves up. 8. Press the down arrow key. 9. Verify the mouse moves down. -Expected Outcome: The mouse moves the appropriate direction that corresponds with the arrow keys.

Test Case 3: Wall Collision -Test Description: Verify that the mouse cannot cross over the wall barriers. -Test Steps: 1. Start the game. 2. Run the mouse into the walls. 3. Verify that the walls act as a barrier. -Expected Outcome: The mouse cannot cross over the walls.

Test Case 4: Item pickup -Test Description: Verify that items can be picked up when ran into. -Test Steps: 1. Start the game. 2. Run the mouse into items. 3. Verify that the item disappears. -Expected outcome: The item disappears when the mouse collides with it.

Test Case 5: Key Functionality -Test Description: Verify the key works when picked up. -Test Steps: 1. Start the game. 2. Pick up the key. 3. Walk to the exit with the key. 4. Verify that the end screen is displayed. -Expected outcome: The end screen is displayed when the mouse goes through the exit with the key.

About

final-project-bestteam-p created by GitHub Classroom

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages