2. Mid Term Sprint - Team

Objective

Complete the provided Express application with your team to view data about a collection of games. The application must include both a server-rendered frontend and a REST API. Due date: March 7th, 2026 at 11:59PM

Getting Started

• To help you get started, a base repository has been provided for you to work from. The repository is set up as a GitHub Classroom Assignment to help you quickly get started.

Steps to Create Your Own Repository

1. Click the link above, and select your team from the list that appears.
2. Click the “Accept this assignment” button.
3. Once your repository is created, clone your new repo to your local machine:

   git clone <your-new-repo-url>
4. Navigate into the project directory and install the necessary dependencies:

   cd <your-new-repo-name>
   npm install
5. Run the app:

   npm start
   This will start the server at http://localhost:3000/.
6. Run tests:

   npm test
   This will run the unit tests for the application.

• By using this template, you’ll have the project structure and initial setup ready to go, so you can focus on building the functionality!
• Note: This code has been provided as a starting point for you to work from. It is by no means a completed project.

Requirements

Data Requirements

• Example data has been included in the base repo, which is more than sufficient for the project, if you wish to use it.
• No additional data sources are required.

Technology Requirements

• You are allowed to use additional npm packages to enhance your application. However, please make sure that any extra packages are relevant and add value to your project.
  • No other packages should be required
    • If you feel the project cannot be completed without an additional package (like express sessions), please reach out, as it means I might’ve made a mistake.
• All pages must be created using EJS templates. Do not use other templating engines (e.g., Handlebars, Pug) or frameworks like React.
• Your application must run on Node.js using Express for the backend.

Functional Requirements

• Data Storage:

  • All data should be stored in memory.
  • No persistence between server runs is required.
  • No user-specific data storage is required.

• Functionality:

  • At minimum, create functions to complete the following:
    • Get x games by genre.
    • Get the y top-rated games, ordered by rating.
    • Get the details of a game by its id.
    • Get a list of “Hidden Gems”
      • Criteria for “Hidden Gems” is up to the team, but a suggestion is games with a high rating but fewer than X reviews.

Unit Tests

Your project must include unit tests to verify that the four core functions—genre filtering, top-rated sorting, game details retrieval, and hidden gems filtering—produce valid output.

At a minimum, your tests should confirm that:

• The genre filtering function correctly retrieves games.
• The top-rated sorting function correctly orders results.
• The game details function properly retrieves data for valid and invalid IDs.
• The hidden gems function produces results that fit the team-defined criteria.

You are responsible for determining the specific test cases needed to verify correct functionality.

Required Pages

• Common Header/Footer:

  • Implemented via an EJS partial.
  • The header should contain navigation links to:
    • Home page
    • Top-rated games page
    • A random game’s page
      • A link the user can click, and when they click it they are brought to the “Game Page” (see below) for a random game
    • Hidden Gems page

• Home Page:

  • Display details of 9 random games.
  • Each game should display:
    • Title
    • Release year
    • Rating (out of 10)
  • Clicking a game (i.e. clicking its title) directs to its details page.

• Top Rated Games Page:

  • Display the 15 highest-rated games, ordered by rating.
  • Each game should display:
    • Title
    • Release year
    • Rating (out of 10)
    • Brief description
  • Clicking a game directs to its details page.

• Game Page:

  • Display detailed game information, including:
    • Title
    • Release year
    • Description
    • Developer
    • Rating (out of 10, unreleased games might not have a rating)
    • Genre
  • Include a recommendations section with three other games based on genre.

• Hidden Gems Page:

  • Display a list of “Hidden Gems”.
    • Criteria for “Hidden Gems” is up to the team, but a suggestion is games with a high rating but fewer than X reviews.
  • Each game should display:
    • Title
    • Release year
    • Rating
    • Short description
  • Clicking a game directs to its details page.

REST API Endpoints

Your project must expose the following REST API endpoints. Ensure that your endpoints return JSON responses using a consistent, standardized response structure (e.g., errors always including an error field). Make sure you use appropriate HTTP status codes.

• GET /api/games

  • Returns a list of all games.
  • Each item should include the title, genre, release year, and rating.

• GET /api/games/:id

  • Returns the full details for the specified game.
  • Returns a meaningful error response if the game ID does not exist.

• GET /api/games/genre/:genre

  • Returns all games matching the specified genre.
  • Returns a meaningful error response if no games are found for that genre.

• GET /api/games/top-rated

  • Returns the top 10 rated games, ordered by rating.

• GET /api/games/:id/recommendations

  • Returns up to 3 recommended games based on the genre of the specified game.
  • Returns a meaningful error response if the game ID does not exist.

Input validation must be applied where appropriate (e.g., unknown IDs, unrecognized genres). Errors must return consistent, structured JSON and appropriate HTTP status codes should be used throughout.

Pass Outstanding Criteria

• Achieve a grade of 85% or above.

Submission Guidelines

• Ensure the application runs correctly (npm start) and all features are implemented.
• Ensure all tests pass (npm test).
• Submit a GitHub repository link on Teams (only one team member needs to submit).
• Late submissions follow the Keyin late assessment policy here.
• If an extension is needed, please reach out before the due date.
• Teams can be a maximum of 3 members

Notes/Questions

• Code samples from class are available here.
• Reach out via Teams or email for questions.
• Support sessions are available during lecture breaks and with the TA.

Grading Rubric