E2E test coverage

Our Cypress test coverage needs expanding. The spec files should go in /cypress/integration which roughly mirrors the routing in /client/src/pages. e.g. cypress/integration/events/[eventId].js contains the tests for client/src/pages/events/[eventId].tsx

Routes needing coverage:

/chapters Does the page exist? Are there links to chapters?

/chapters/[chapterId] Is there an event list?

/dashboard/events/ Can you add sponsors to an event? Once they’ve been submitted, can you see them on the event page? We can use the same approach as for @venueTitle https://github.com/freeCodeCamp/chapter/blob/c608045b8265c7fd51a9b496d03a1a942babd019/cypress/integration/dashboard/events.js#L48-L51

/dashboard/events/[id] Can you kick users? Can you confirm them?

/events/[id] When someone RSVPs for the first time, do they become a chapter member? Do they get signed up for notifications?

If an existing user who has opted out of notifications RSVPs are their notification settings maintained?

[ojeytonwilliams]

@Ismailtlem you can go ahead with this if you wish. There’s never going to be an excess of test coverage.

[ojeytonwilliams]

@Ismailtlem I think we’ll want to be working on this periodically, but I don’t think this needs to stay open.