Oliver Eyton-WilliamsandShaun Hamilton
d7848ae01a
* feat: npm -> pnpm This resolves the issues with the gatsby client (gatsby-plugin-pnpm deals with the fact that gatsby is relying on its own dependencies being de-duped) and challenge-editor (which doesn't seem to want to automatically install codemirror and needed its own eslint config) * fix: correct mocha path for curriculum tests * fix: use select workspace with -F not -w * fix: reorganise packages and restrict hoisting pnpm works best if the workspaces keep their own dependencies, since dependencies are not flattened and then what node resolves from a require is predictable. @types seem to be a special case and more care is required to prevent them getting smushed together in the root (hence the .npmrc) * fix: add types for tools + root * fix: decouple challenge-auditor from client * fix: add ui-components types * fix(client): use the latest types for react 16 * fix: prettify * fix: prettierignore pnpm-lock * fix: relax hoisting Turns out pnpm works just fine with types. I don't know what was going wrong before, but there are no-longer any type conflicts. * fix: add @redux-saga/core to fix eslint issue It seems to only be redux-saga that import/named can't cope with, so it is probably okay to work around this one. * chore: add chai to tools/scripts/build * fix: add store to root for cypress * fix: allow cypress to download binaries If we want to keep preventing cypress from downloading binaries, we can figure out a workaround, but I'm allowing it to ease the transition to pnpm. My guess about why this is happening is that npm triggers Cypress's postinstall script, but pnpm does not (because pnpm install only installs if necessary, perferring to link) * chore: re-enable pre/post scripts * fix: update build scripts for client Co-authored-by: Shaun Hamilton <shauhami020@gmail.com> * chore: update engines to use pnpm * fix: enable choice of (super)block for tests Only 'nix machines for now. * chore: pin pnpm to version 7 * chore: remove last npms Except web + curriculum-server. I'll update them when I start work on them again. * fix: lockfile check to catch any package-locks * fix(action): install pnpm for upcoming tests * chore: add nodemon to new api Co-authored-by: Shaun Hamilton <shauhami020@gmail.com>
2.2 KiB
How to add Cypress tests
When making changes to JavaScript, CSS, or HTML which could change the functionality or layout of a page, it's important to add corresponding Cypress integration tests.
To learn how to write Cypress tests, or 'specs', please see Cypress' official documentation.
Where to add a test
-
Cypress tests are in the
./cypressdirectory. -
Cypress tests for a curriculum module are in the corresponding curriculum directory, i.e.
cypress/integration/learn/responsive-web-design/basic-css/index.js.
How to run tests
Note
If using GitPod, please see Cypress-GitPod Setup
1. Ensure that MongoDB and client applications are running
2. Run the cypress tests
To run tests against production builds, replace dev with prd below.
-
To run all tests in the
./cypressdirectory:pnpm run cypress:dev:run -
To run a single test:
pnpm run cypress -- run --spec=cypress/<path_to_test_file>For example:
pnpm run cypress -- run --spec=cypress/e2e/default/landing.js -
To create a development build, start the development server, and run all existing cypress end-to-end tests:
pnpm run e2e:dev:run
Cypress-GitPod Setup
1. Ensure Development Environment is Running
If starting the GitPod environment did not automatically develop the environment:
- Start the database
mongod
- Seed the database
pnpm run seed
- Develop the server and client
pnpm run develop
2. Install Cypress Build Tools
pnpm run cypress:install-build-tools
- When prompted in the terminal, select your keyboard layout by language/area
Now, Cypress can be run