Closed rob-howells closed 1 year ago
@iamsophiesk @AccessPaul I've added an 'on hold' label to this work, since after Lewis' demo at the dev meeting, it looks like lot of work has already been undertaken by the QA team to build Cypress into their workflow (and so adding Cypress to the theme may no longer be the most appropriate place for it). Further team discussion is required to figure out a solution for having a consistent Cypress implementation (or at least an option to enable Cypress) for each new suitable project
Background / motivation
Approach
test:local
NPM script, which runs test scripts headlessly. Note there are options for running this within a browser too (see attached)cypress/integrations/main-menu.js
), which tests opening and closing the mobile menu. Note - the remaining folders in thecypress
directory are scaffolding files automatically created by Cypress each time it initialisesAdditional work
eslint
andprettier
NPM scripts to check all JS files in theme (excluding those in.eslintignore
and.prettierignore
)eslint
andprettier
to update any JS files in theme to appropriate standardsNext steps
If people feel like this would be a worthy addition to the theme, explore how we could run Cypress tests via CI (rather than just locally)