# Nom Nom App  --- App to leave reviews on restaurants  --- ## Roles - Orian: Quality Assurance - Juliette: Dev Ops - Paolo: UX Lead & Scrum Facilitator --- ## How we split the work --- ### Day 1 - Orian - Project setup: Juliette and Orian - Installing dependencies - Setting up local database - Write CSS and basic HTML structure - Paolo - Create schema on [dbdiagram.io](https://dbdiagram.io/home) - Build database and insert mock data in `init.sql` file - Write first test for homepage navigation --- ### Day 2 - Juliette - Merged CSS and static files - Added get and post functions so form entries were rendered on page - Wrote test for to check form submitted review and added it to the home page - Added basic post query - Simplified schema from one table to three - Added security to stop SQL injection - Deployed to Heroku --- ### Instagram:  --- ### VS Reality  --- ## Dev Ops - Setting up file structure - This definitely took longer than anticipated! - __Always__ set up your`.gitignore` first! - Then your `.env`  --- - Deploying to Heroku - Encountered some issues... - SSL errors and installed Heroku command line to understand better  --- - Attempted to set up Github Actions! - This was a stretch goal of ours :straight_ruler: - It was fun to try and set these up, even if we didn't manage to get our tests working yet --- ## Quality Assurance :first_place_medal: - TDD with Cypress - Implement DB reset before each test - Insisting on clean code - Improvements: - Write more tests :pencil: - Questions to research: - Can you query database directly with SQL in test? --- ## Ux Lead & Scrum Facilitator ---- ## Project Board DAY 1  ---- ### DAY 1 Estimate vs Actual Velocity  Estimate 8pts / Actual 9pts ---- ## Project Board DAY 2  ---- ### DAY 2 Estimate vs Actual Velocity  Estimate 14pts / Actual 12pts ---- ## Key Learnings - Don't forget to create `.gitignore` in project setup. Once files are pushed to github it is too late... - Communicate, communicate, communicate --- ## We are proud of ... :crab: - Having deployed our first database project on Heroku! - Taking time to understand errors and imrpove our debugging skills :bug: - Team work: we had a few bumps in the road but we were open and honest with each other throughout the process! --- - Attempting using gitHub actions - Learning the basics on how to represent database tables on dbdiagram.io --- ## What we could have done ... - Code modularisation - Error handling - Use more than one table in our db - Grouping tests using describe --- ## Core user stories * As a user, I want to: submit information to your site for anyone to see * As a user, I want to: come back to your site later and see what I posted is still there --- [Demo](https://nom-nom-app.herokuapp.com/):link: