isleofyou / lemon-aide Goto Github PK

As a user, I should see my outfits properly displayed whether I'm on my phone or desktop computer.

Need a test for the following user story:

• As a user, when I visit the favorites page the URL should be "/favorites".

• As a user, when I visit the favorites page I should only see items that I have favorited.

As a user, when I click on any of the contributor's LinkedIn or GH icons I should be navigated to their respective profiles.

Need a test for the following user story:

• As a user, when I visit the favorites page and I haven't favorited any products I should see a div that tells me to "Add favorites to see them here.

• As a user, when I click on the header's logo I should be navigated to the homepage.

--You can use useNavigate on the Header component and onClick of the logo image, it will navigate the user to the homepage. Alternatively, you may also be able to wrap it up with a Link.

• We will also need to test this functionality

As a user, when I first visit the homepage and do not see any of the products in the products container (or see them loading slowly) I should see a loading icon that rotates in the products container until the fetch Promise for all products has resolved (component mounts) and renders the products in the container.

As a user, when I only have 1 or 2 favorited products I should see those products displayed on the favorites page correctly.

• Update display of 1 favorited product:

• Update display of 2 favorited products:

• As a user, when I scroll all the way down I should see a footer that shows the names of all the contributors and links to their GH and LinkedIn profiles via each site's logo.

• We will also need to test this functionality.

I created a custom octocat on https://myoctocat.com/build-your-octocat/...it didn't actually email me what I built but I took a screenshot and then went to https://www.remove.bg/ to remove the white background.

As a user, when I visit the homepage and any other page I should be able to see a Hamburger icon (the Aside component) with the links to each page and click on the page that I want to be navigated go to.

Ideally the aside component will stay on the left hand side and will be underneath the Header component.

Need a test for the following user story:

• As a user, when I visit the homepage the URL should be "/".

• As a user, when I click on the aside's "All Items" link, I should be directed to the homepage.

As a user, when I visit the homepage and am not able to see any of the products or content I should see an Error message (Component) with the attached picture describing why (Whoops! /n Error: (error msg from state property in App.js)).

.

Need a test for the following user story:

• As a user, when I visit the home, favorites or outfits page and the server's response is not okay I should see an Error component.

Need a test for the following user story:

• As a user, when I visit the homepage and the products are still being rendered I should see a Loading component.

• Create a README file for our repository.

Here is some content that I was able to sketch out for the FE's README:

Technologies

• React
• Postgres
• Knex
• HTML
• CSS
• JavaScript

FE Enhancements

1. FE Local storage for items in cart
2. FE Have carousel for each item category
3. FE Have the cart items show up in the order that they are selected

FE Challenges

1. Accidentally committing node modules and branching off of that branch caused them to persist until we created a git ignore file and removed them from every branch that was being merged. Unfortunately this skewed our contributions for lines of code that were written and deleted but the number of commits accurately depict that metric.
2. Accidentally committing node modules and removing them also caused one of our 3 group members to be on a different version of node which became an issue when attempting to run our Cypress tests. Fortunately this was fixed by having her uninstall and reinstall the correct version of node.
3. Eight day timeframe to learn about and implement a backend server, database and frontend application with 2 features.
4. Having so many modes of communication made it difficult for some of our team members to understand and remember what they were supposed to be working on. Luckily GH issues became a much better place to draw out, reference and delegate tasks.

FE Wins

1. Successfully being able to divide and conquer tasks and complete them in a timely manner.
2. Having at least two people pair and walk through a PR, request changes and gracefully making changes before the branch was merged to main.
3. Learning CSS tricks, useState, and different ways of doing things from each other’s work.
4. Our “your win is my win” attitude really guided us through many hiccups and disagreements.