/burrito-builder-ui

Primary LanguageJavaScript

Burrito Builder UI

Our company is building a prototype ticketing system for a local burrito shop. Unfortunately, the form dev on the project recently quit, leaving behind a broken app and little to no documentation. It's your job to save the project!

Setup

  • Fork this repo
  • Clone down your forked repo and change into the cloned down directory
  • Run npm install to install dependencies
  • Run npm start to start your development server

Be sure to setup the backend repo for Burrito Builder to be able to retrieve and save burrito orders.

Iterations

Iteration 1

Right now the app has serveral bugs in it. Run the dev server and fix whatever bugs are causing the app to crash.

Iteration 2

Connect the front end to the backend so that when the app loads, all existing orders are fetched from the server.

Iteration 3

Add functionality to allow submission of the form when there is at least once ingredient, and a name added to the order. If one of these two things is missing, you should not be able to submit an order. If the order is submitted, a POST request should be made to the server.

New orders should only be displayed on the page IF the POST request is successful. On refresh, the new order should persist on the page. (You shouldn't need to refresh the page to see the new order, though.)

Iteration 4

Write Cypress tests for the following user flows (don't forget to stub your network requests):

When a user visits the page, they can view the page title and the existing orders When a user visits the page, they can view the Form with the proper inputs When a user fills out the form, the information is reflected in the input field's value

Extensions (only to be attempted if all prior iterations are complete)

  • Add delete functionality for an order (the server-side endpoint exists already) so that when the order is ready it can be removed from the ticketing system.
  • Test the deleting functionality.
  • Right now, an order can contain duplicates of ingredients. Bring some logic into the form so that an order can contain only two of the same ingredient.
  • Add a total cost for the order. Add prices to each ingredient and total each order based on the ingredient cost. Display this for each order. The backend should be able to handle any extra data beyond name and ingredients.
  • Style the form - it's hideous, and the team is sad about it.
  • Style the container so that orders are nice and tidy, especially when ingredient amounts vary between orders.

This project was bootstrapped with Create React App.