Background and Description

For this project, you will be building a hotel management tool for hotel customers and staff to manage room bookings and calculate customer bills.

Goals and Objectives

• Use OOP to drive the design of the application and the code
• Work with an API to send and receive data
• Solidify the code review process
• Create a robust test suite that thoroughly tests all functionality of a client-side application

Timeline

Dates and deadlines to be aware of:

Day One Deliverable: Please submit your project here

Tuesday, Week 6 - Project due at 9PM.

Requirements

Technologies

• the fetch API to retrieve and add data
• Mocha and Chai for testing your code

Initial Setup

For this project, you will want to use this Webpack Starter Kit repo. Setup instructions are in the README. You will also need to clone down this local server and have it running in a separate tab in your terminal each time you run your client.

Endpoints

Below are all the endpoints set up for this project. You may not use all of them. Pay attention to the functionality required of each iteration when picking the appropriate endpoint.

Iterations

1. Dashboard

As a customer:

• I should see a dashboard page that shows me:
  • Any room bookings I have made (past or upcoming)
  • The total amount I have spent on rooms

2. Customer Interaction

As a customer:

• I should be able to select a date for which I’d like to book a room for myself
• Upon selecting a date, I should be shown a list of room details for only rooms that are available on that date
• I should be able to filter the list of available rooms by their roomType property
• I should be able to select a room for booking
• In the event that no rooms are available for the date/roomType selected, display a message fiercely apologizing to the user and asking them to adjust their room search

Refer to the “Add new booking” section from the endpoints table above!

3. Accessibility

• Create a branch for accessibility.
• Use this branch to make your dashboard as accessible as possible.
• Push this branch up to GH. You can merge the changes into main but do not delete this branch.
  • This branch should not have a login page so that during the live eval, we can run the Lighthouse audit and check tabbability of your dashboard (without the login page).

4. Login

When first arriving at the site, a user should be able to log in with a username and password.

As a customer:

• I should be able to login
  • I will see a login page when I first visit the site
  • I can log in with the following credentials:

username: customer50 (where 50 is the ID of the user)
password: overlook2021

• Upon successfully loggin in, I should see my dashboard.

Refer to the “Get single user” section from the endpoints table above!

5. Manager Interaction

Your app should now support two different types of users. In addition to having a customer, you will now add a manager.

As a manager:

• I should be able to login
  • I will see a login page when I first visit the site
  • I can log in with the following credentials:

username: manager
password: overlook2021

As a manager, upon logging in:

• I should see a dashboard page that shows me:
  • Total Rooms Available for today’s date
  • Total revenue for today’s date
  • Percentage of rooms occupied for today’s date

As a manager:

• I should be able to search for any user by name and:
  • View their name, a list of all of their bookings, and the total amount they’ve spent
  • Add a room booking for that user
  • Delete any upcoming room bookings for that user (they cannot delete a booking from the past)

Refer to the endpoints table above for deleting a single booking

Testing

You should be testing the correctness of your code throughout your project. Each JavaScript class file in your project should have its own test file.

Your testing suite should test:

• Class properties
• Class methods

Remember to test all possible outcomes (happy/sad/etc). Ask yourself:

• What is the value of each property?
• Does the method return anything?
• Does the method update any properties?
• Are there different possible outcomes to test for based on different arguments being passed in?

You are not expected to test:

• DOM manipulation / DOM manipulating methods (like document.querySelector(...))
• Fetch calls

Workflow

You will want to submit PRs to your accountabilibuddy to:

• You must give your accountabilibuddy collaboration access to your repo.
• You must submit at least 2 PRs to your accountabilibuddy for review.
• You must wait for your accountabilibuddy to review your PRs, and allow THEM to merge any PRs you submit.

It is up to you to decide what changes warrant a PR – remember we want to submit PRs that have significant changes and potential for feedback. Think about what functionality you’re struggling with or have questions about or need help with. As an accountabilibuddy, you are responsible for reviewing at least 2 PRs from your partner.

Please also tag your project manager in any PR you make to your buddy.

Accessibility

• Accessibility audits should be at 100% for the dashboard.
• A user should be able to interact with all functionality of your application by tabbing through it, no use of the trackpad
• ARIA attributes should be utilized for any UI elements that are not understood by the screen reader

Due Date

Make sure you submit your project here by Tuesday of Week 6 at 9pm.

Rubric

Specification Adherence

• 4: The application completes all iterations above without error.
• 3: The application completes the first 4 iterations above without error. Note: Must be completed in order to pass.
• 2: The application completes the first 2 iterations and is in a usable state, but has some miscellaneous bugs.
• 1: The application completes only the first iteration, displaying the user’s data, but has no additional functionality.

UI/UX & Accessibility

• 4: Application has clearly had special consideration around accessibility. Lighthouse accessibility audit is at a 100% and application is fully tabbable.
• 3: Application has many strong pages/interactions. The application can stand on its own to be used by instructor without guidance. The UI does not detract from the UX. Lighthouse accessibility audit is at least 90% and application is fully tabbable.
• 2: The application may be confusing or difficult to use at times. The UI is incomplete. Accessibility has been considered, but does not have strong accessible features.
• 1: Application is confusing or difficult to use. The UI is incomplete. Accessibility has not been considered.

JavaScript Style & OOP

• 4: Application has exceptionally well-factored code with little or no duplication. The business-logic code driving functionality is cleanly separated from rendering, view-related code. Excellent usage of fetch and updates DOM based on results of network requests. Handles all scenarios for error handling.
• 3: Application is thoughtfully put together with some duplication. Application is organized into classes with some misplaced logic. Business-logic code is mostly separated from view-related code. Great usage of fetch and updates DOM based on results in most scenarios, but may update DOM before a network request is complete. Handles most scenarios for error handling.
• 2: Class methods use a mix of array and object prototypes and for loops. Application runs but the code has long methods, unnecessary or poorly named variables, and needs significant refactoring. Uses fetch effectively for GET but does not implement POST. Has little error handling and only console logs errors if a network request fails.
• 1: Application generates syntax error or crashes during execution. Application is not separated into classes and there is no separation of business-side logic and view-related code. Developer writes code with unnecessary variables, operations, or steps that do not increase clarity.

Testing

• 4: Application covers all aspects of the application including various flows and covers both happy/sad paths. Tests must be passing to be considered.
• 3: Application is well tested but fails to cover some features and only tests for happy paths. Tests must be passing to be considered.
• 2: Project has sporadic use of tests at multiple levels. The application contains numerous holes in testing and/or many features are untested. Tests must be passing to be considered.
• 1: There is little or no evidence of testing in the application.

Evaluation

Evaluations will be done live with an instructor. You’ll be asked to step through the various parts of your application including accessibility audit, the user interface, running tests and looking at fetch calls and JavaScript code.