1. Mid Term Sprint - Solo

Objective

Complete the provided Express application independently to generate fictional travel itineraries. 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 Assigment to help you quickly get started.

Steps to Create Your Own Repository

1. Click the link above, and select your name on the list that appears, if you haven’t already

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

• When the application starts, generate a random itinerary for each location.

• Itinerary Requirements

  • The application should generate fictional travel itineraries (see below)
  • When the user visits the homepage a random featured itinerary should be displayed
  • Users should be able to select a destination from a dropdown to view a more detailed itinerary for that location.

• Functionality At minimum, implement the following functions:

1. Generate an Activity
   • Generates an activity with:
     • A name
     • A brief description
     • A randomly generated price
     • Whether it’s a “highlight activity” (randomly determined)
2. Generate a Full Itinerary
   • Creates an itinerary for a selected destination with 3-7 activities.
   • An intinerary shouldn’t contain duplicates of an activity.
   • The number of activities on an itinerary should be randomly selected, but should somewhere between 3-7 activities
   • Calculates the total estimated trip cost.

You may create additional functions beyond these requirements, but at minimum, the above functions must be implemented.

Unit Tests

Your project must include unit tests to verify that the core functions outlined above work correctly and produce valid output

At a minimum, your tests should confirm that:

• The activity generation function produces an activity with all required properties and appropriate value types/ranges
• The itinerary generation function creates an itinerary that contains between 3–7 activities, contains no duplicate activities, and correctly calculates the total cost.

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

Required Pages

Home Page

• Include a dropdown that allows a user to select a destination for a more detailed itinerary.
  • Selecting a destination redirects them to the “Itinerary Page” (see below).
• Display a random featured itinerary when the page loads.

Itinerary Page

• Display the full itinerary for the selected destination.
• Each itinerary should include:
  • The destination name
  • List of activities
  • Estimated total budget

REST API Endpoints

Your project must expose the following REST API endpoints. Ensure that your endpoints return JSON responses that are consistent using some type of standardized response (i.e. errors always having an error field). As well, make sure you use appropriate HTTP status codes.

• GET /api/itineraries
  • Returns a list of all generated itineraries (one per destination).
  • Each item should include the destination name, number of activities, and total cost.
• GET /api/itineraries/:destination
  • Returns the full itinerary for the specified destination.
• GET /api/itineraries/:destination/highlights
  • Returns only the highlight activities for a given destination’s itinerary.

Input validation must be applied where appropriate (e.g., unknown destinations, malformed parameters), errors must return consistent, structured JSON and proper HTTP status codes should be returned

Pass Outstanding Criteria

• Achieve a grade of 85% or above.

Submission Guidelines

• Ensure the application runs correctly using npm start, and all features are implemented as specified.
• Ensure all tests pass using npm test.
• Submit your GitHub repository link on Teams under the appropriate assignment.
• Late submissions will follow Keyin’s late assessment policy.
• If an extension is needed, please reach out before the due date.

Notes/Questions

• You can find examples from class here.
• If anything is unclear or you need help, reach out on Teams or via email.
• Support sessions are available during lecture breaks and with the TA.

Grading Rubric