This codebase needs CI/CD on pull requests so devs can see all green and feel better about merging them in. One of the main components of this is Cypress end-to-end testing.
I was planning to have the first test be with authentication, but that should really be stubbed via a fake cookie...and it's far easier just to create a page that will be used, /admin/[space]/content -> ContentOverview, and keep it blank for now. This will also help to test out more complicated dynamic routing setups.
Required
What area of the codebase does this involve?
Automated Testing
Credential Management
Will this impact CI/CD procedures?
Yes, this issue is to set up the whole process via Cypress. Then, other issues would add more GH checks on pull requests.
Relate To Security?
I had to add secrets for the app to yarn build since it builds out the profile page, which touches Auth0 connection code.
Acceptance Criteria
[x] When a pull request is made, a Cypress test runs.
[x] Users can go to /admin/ir20/content and see "Content Overview for the ir20 space" as the page title.
This codebase needs CI/CD on pull requests so devs can see all green and feel better about merging them in. One of the main components of this is Cypress end-to-end testing.
I was planning to have the first test be with authentication, but that should really be stubbed via a fake cookie...and it's far easier just to create a page that will be used,
/admin/[space]/content -> ContentOverview, and keep it blank for now. This will also help to test out more complicated dynamic routing setups.Required
What area of the codebase does this involve?
Will this impact CI/CD procedures?
Yes, this issue is to set up the whole process via Cypress. Then, other issues would add more GH checks on pull requests.
Relate To Security?
I had to add secrets for the app to
yarn buildsince it builds out the profile page, which touches Auth0 connection code.Acceptance Criteria
/admin/ir20/contentand see "Content Overview for the ir20 space" as the page title.