# Moo-net 🐮 ---  --- ## Facilitator role 🚦💁🏾 * Made good use of the kanban board right from the start * Used labels to designate tasks * We made our user stories the core focus of our tests and our approach to the project --- ## UX role 👨🏽‍🎨🎨 * Mobile first design with flexbox and setting responsive widths * Considered the order of posts and added date/time * Made use of box-shadow, keyframe animations, favicon and accessibile hover states ---  --- ## Quality Assurance role :cow::chart_with_upwards_trend: * TDD approach and *its effectiveness.* * Appropriate naming of variables. * Use of cypress. * Sanitisation of input. * How tests can influence each other. ``` cowPostObj.message.replace(/>/g, "'&lt';"); ``` --- ## 404 redirects test :-1: ``` it("can display 404 if page not found", () => { cy.request({ url: "/page-not-found", failOnStatusCode: false }).should( (response) => { expect(response.status).to.eq(404); } ); }); ``` --- ## Cypress.$ :rainbow: ``` cy.visit("/"); cy.get("body") .find("li") .then((list) => { //starting length currentListLength = Cypress.$(list).length; }); ``` ---  --- ## DevOps role :hammer_and_wrench: * Project set up: - correct file structure - install express and nodemon dependencies - install cypress dev dependency - write and run scripts in `package.json` - resolve unrelated commit histories with `git force push` because remote and local were not set up correctly * Deployment on Heroku --- :clock1: ### With more time we would have implemented... * Project modularisation * 'Like' button * Editable user posts --- ## Team learnings * Reviewed our way of working and changed the style. * After the first day we switched to a 'driver': 'navigator' style of pair programming * Kanban board and keeping everyone on same page helped with github workflow * We worked together on most issues, but did split into groups for error route handling and css --- ## Demo