tamaradimov / recipe_app_ror Goto Github PK

• Use Capybara to write integration tests for each view in your project.

• Think about the flow of things and group the tests of the page in a way that makes sense. For example, one test would check for the things on the page, and another test for clicking links on it.

• Be sure to include integration specs for any other features you may have implemented!

Create a navigation menu that allows users to open all of the pages you created.

• create the recipe App

• setup linters and devise gem

• Should show the list of food that is missing for all recipes of the logged-in user (compare the list of food for all recipes with the general food list of that user).
• Should count the total food items and total price of the missing food.

• Can register a new user.
• User logs in with a combination of email and password.
• Hashed password should be stored in the database.
• Ask for confirmation of email.
• Can reset password.

• Add RSpec as a gem to your project.

• Create a Request spec file for all your controllers.

Make sure that for each action you check:

• If response status was correct.

• If a correct template was rendered.

• If the response body includes correct placeholder text.

Make sure there are no N+1 queries happening

• We are a team of 2 members @TamaraDimov and @Salimer

• Kanban board with all the tasks according the requirements

• Should display a toggle button that allows for a recipe to be made public or private.
• If the recipe is public or the user is the owner of the recipe, should display the recipe details as in the wireframe.
• If the user is the owner of the recipe, should lead to the form that allows the user to add new food.

• Should display a list of recipes created by the logged-in user as in the wireframe.
• Should lead to recipe details.

• Should display a list of all public recipes ordered by newest as in the wireframe.

• Should lead to recipe details.

• Should display a list of food added by the logged-in user as in the wireframe (display also quantity of a given food).
• Should lead to a form that allows users to add new food.
• If the user is the owner of the recipe, should allow the user to delete it.