-
Notifications
You must be signed in to change notification settings - Fork 0
User Stories
User Story
As a Project Manager, I want to see a completed Readme file so that I can understand more about your project.
Acceptance Criteria
- Readme located at the root of your project has been updated with info from the wiki.
User Story
As a Project Manager, I want to see an updated favicon so that I can easily identify your application in a list of tabs.
Acceptance Criteria
- Favicon has been updated from the default icon provided by the project starter.
User Story
As a Developer, I want to deploy my starter app to Heroku so that I can make sure I can deploy changes consistently.
Acceptance Criteria
- The cloned starter app has been deployed to Heroku.
User Story
As a Developer, I want to display links to my GitHub and LinkedIn profiles so that prospective hiring managers can learn more about me after looking at my project.
Acceptance Criteria
- Links to my LinkedIn and GitHub profiles will appear on the homepage of my application
User Story
As a User, I want to create an account so I can use the website.
Acceptance Criteria
- A link/button appears in the navigation for Sign Up (only when not already logged in)
- When clicking the link/button the user is redirected to a sign up form.
- After filling out the form and clicking a Submit button an account is created.
- The user is redirected to the landing page
- The user has some indication that the user is now logged in.
User Story
As a User, I want to login with my previously created account so I can use the website.
Acceptance Criteria
- A link/button appears in the navigation for Log In (only when not already logged in)
- When clicking the link/button the user is redirected to a login form.
- After filling out the form with username and password and clicking a Login button the user is logged in.
- The user is redirected to an appropriate page (determined by the developer)
- The user can visually identify they’ve been logged in by having their username displayed in the navigation bar.
User Story
As a Developer, I want to validate the LogIn/Signup forms being submitted so my users have a good experience when using my application.
Acceptance Criteria
- (Log In) If the username/password combination is wrong, or the user does not exist the login fails.
- (Log In) A message is displayed to the end user indicating which fields are invalid.
- (Sign Up) If the username/email already exists, the signup form fails
- (Sign Up) A message is displayed to the end user indicating which fields are invalid.
User Story
As a Logged In User, I can log out of my account so I can ensure it isn’t used without my permission.
Acceptance Criteria
- A link/button appears in the navigation for Log Out (only when logged in)
- When clicking this button/link the session ends and the user is logged out.
- When refreshing the page or traveling to other pages the user does not appear to be logged in
- The logged out user can log in with a separate account without issue.
User Story
As a Project Manager, I can use a Demo Account so that I can use the application without having to use the signup form.
Acceptance Criteria
- A link/button appears in the navigation form and/or Login Form titled “Demo” (only when logged out)
- When clicking this button/link the user is automatically logged in as a Demo User (a previously created account for testing) without the need to fill out the signup/login form.
- The user is redirected as if they successfully completed the Log In form.
User Story
As a User, I would like to see at least basic styling on the signup and login forms so that the application doesn’t appear too similarly to the default application provided.
Acceptance Criteria
- Sign up and Login forms have been styled appropriately.
User Story
As a User (logged in), I want to create a restaurant page so I can share details about it.
Acceptance Criteria
- A link/button appears in the navigation for adding a restaurant “add restaurant” (only when already logged in)
- When clicking the link/button the user is redirected to the add restaurant form.
- After filling out the form and clicking a Submit button a restaurant is created.
- The user is redirected to the restaurant page
User Story
As any user, I want to see a restaurant’s page so I can learn more about it.
Acceptance Criteria
- From the search/category page, the user can click on the restaurant and be redirected to the restaurant page
- The user can see details about the restaurant, photos, reviews, and a map of its location
User Story
As a user (logged in, who created the restaurant) I should be able to update the restaurant’s information including hours, name, description, and location.
Acceptance Criteria
- A logged in user should see a button to update the restaurant page
- When clicked, the user will be redirected to an update restaurant form, where they can update the restaurant’s details
- Once updated, the user can click the submit button or cancel.
- submit will update the changes and redirect the user to the restaurant’s page
- cancel will NOT update any changes and the user will be redirected to the restaurant’s page
User Story
As a user (logged in who created the business), you should be able to delete the restaurant’s page.
Acceptance Criteria
- A logged in user (the one who created the business page) should see a button to delete the restaurant page
- When clicked, the user will be redirected to the landing page
- Logged in users, a user who hasn’t created the restaurant page, will not see a delete button
User Story
As a Developer, I want to validate the Add Restaurant/Update Restaurant forms being submitted so my users have a good experience when using my application.
Acceptance Criteria
- (name) If the restaurant name input is not present the name fails.
- (name) A message is displayed to the end user indicating which fields are invalid.
- (address) If the restaurant address input is not present the address fails.
- (address) A message is displayed to the end user indicating which fields are invalid.
- (city) If the restaurant city input is not present the city fails.
- (city) A message is displayed to the end user indicating which fields are invalid.
- (state) If the restaurant state input is not present the state fails.
- (state) A message is displayed to the end user indicating which fields are invalid.
- (zip code) If the restaurant zip code input is not present the name fails.
- (zip code) A message is displayed to the end user indicating which fields are invalid.
User Story
As a User, I would like to see at least basic styling on the add and update restaurant forms so that the application doesn’t appear too similarly to the default application provided.
Acceptance Criteria
- Add and update restaurant forms have been styled appropriately.
UserStory
As a user (logged in), you should be able to create a review on the restaurant’s page.
Acceptance Criteria
- A logged in user should see a button to add a review to the restaurant page
- When clicked, the user will be redirected to the add review page
- A user can fill out their review, rating, and answer
- The user can then click the submit or cancel button
- submit will accept the new review and the user will be redirected to the restaurant page and their review will be shown
- cancel will not add any review and will redirect the user back to the restaurant’s page
UserStory
As a user (logged in), you should be able to read a review on the restaurant’s page.
Acceptance Criteria
- All users should be able to see reviews on the restaurant’s page
UserStory
As a user (logged in), you should be able to update a review on the restaurant’s page.
Acceptance Criteria
- A logged in user who previously submitted a review, you should see a button to update your review for the restaurant.
- When clicked, the user will be redirected to the update review page
- A user can fill out their updated review, rating, and answer
- The user can then click the submit or cancel button
- submit will accept the new review and the user will be redirected to the restaurant page and their review will be shown
- cancel will not add any review and will redirect the user back to the restaurant’s page
User Story
As a user (logged in who created the review), you should be able to delete your review.
Acceptance Criteria
- A logged in user (the one who created the review) should see a button to delete their review.
- When clicked, the user will no longer see the comment rendered on the restaurant’s page
User Story
As a Developer, I want to validate the Add/Update Restaurant forms being submitted so my users have a good experience when using my application.
Acceptance Criteria
- (rating) If the restaurant rating input is not present the rating fails.
- (rating) A message is displayed to the end user indicating which fields are invalid.
- (review) If the restaurant review input is not present the review fails.
- (review) A message is displayed to the end user indicating which fields are invalid.
User Story As a User, I would like to see at least basic styling on the add and update review forms so that the application doesn’t appear too similarly to the default application provided. Acceptance Criteria
- Add and update reviews forms have been styled appropriately.
UserStory
Any user should be able to search for restaurants to find their desired restaurant/category and see a results page. Acceptance Criteria
- The user can look up the restaurant by name or category in the search bar
- After entering the information in the search bar/selecting a category the user will be redirected to the search page/category page, which will show restaurants
- When clicking the restaurant, the user is redirected to the restaurant page
UserStory
A logged in user should be able to add images for restaurants to be shown on the restaurant’s page, and restaurant images page
Acceptance Criteria
- A logged in user should see a button to add a photo on the restaurant’s images page.
- When clicked, the user will be redirected to an add image form where they can input the url of the image they’d like to show on the restaurant’s page and restaurant’s images page
- Once the user adds the url they can click submit or cancel
- submit will accept the new image and the user will be redirected to the restaurant’s images page
- cancel will not add any image and will redirect the user back to the restaurant’s images page
UserStory
A user can see images for a given restaurant.
Acceptance Criteria
- Any user should be able to see images for a restaurant
UserStory
A logged in user (who added an image) should be able to delete an image/images they added for the restaurant.
Acceptance Criteria
- A logged in user (the one who added the image) should see a button to delete their image.
- When clicked, the user will no longer see the image rendered on the restaurant’s images page or the restaurant’s page
User Story
As a Developer, I want to validate the Add Restaurant Image form being submitted so my users have a good experience when using my application.
Acceptance Criteria
- (imageUrl) If the imageUrl input is not present the name fails.
- (imageUrl) A message is displayed to the end user indicating which fields are invalid.
User Story
As a User, I would like to see at least basic styling on the add restaurant image forms so that the application doesn’t appear too similarly to the default application provided.
Acceptance Criteria
- Add restaurant image form has been styled appropriately.