Skip to content

testing.md

Latest commit

 

History

History
91 lines (48 loc) · 4.91 KB

testing.md

File metadata and controls

91 lines (48 loc) · 4.91 KB

Testing

Jest for unit testing

Supporting server-only tests

We support server and client testing based on the following naming convention:

  • A test named myTest.test.ts will be executed in a JSDOM environment (~ like a browser). Use as a default for React components and generic utility code.
  • A test named myTest.test.server.ts will be executed only in the Node server environment. Use to test your Graphql resolvers for instance.

React Testing library

We have preinstalled React Testing Library and React Testing Hooks.

Tests for Vulcan Next (for contributors only)

We have a unit tests for some key features and scripts of VN, through the tests/vns folder.

This folder is ignored when running yarn run test:unit, to avoid bloating your own tests.

MDX parsing, magic imports with ~

jest-transformer-mdx allow importing .mdx also in Jest

Unified testing patterns

We strive to unify testing patterns between Cypress and Jest where it makes sense.

First, add React Testing queries into Cypress, so you can fetch elements with similar patterns. Check React Testing docs for example of the reverse approach (data-cy in React Testing).

Unified test coverage

We followed awesome recommandations from Bahmutov to unify Cypress and Jest coverage. This is crucial to have a clearer vision of what is correctly tested in your application, whatever the test method is. For instance, e2e tests provides a huge coverage for React components, while unit tests are more efficient for helpers, hooks and functions.

yarn run coverage will run tests and compute the unified report in coverage.

yarn run reports:combined will compute the combined report without running tests.

More insights with Cypress

Cypress for e2e testing

TypeScript and vanilla JS (+ESLint)

Custom commands, with TypeScript

Relevant doc

You can write JavaScript tests and still enjoy auto-completion of custom commands, thanks to TS triple slash directives.

Reuse app Webpack config

You may want your Cypress code to be as powerful as your app code. For this, we are enhancing the Cypress webpack config with the same features as in the app.

Example from Cypress with TS + Webpack

Code coverage

See Cypress Code Coverage example for TS, Cypress Next example, Cypress TS example...

Note: doc of NYC for TS has to be followed carefully (computing sourceMaps for TS code, installing all sibling packages...). The difficult part is instrumentation.

Code coverage is totally disabled client-side when simply running tests, using "CYPRESS_coverage" variable (thanks @bahmutov).

No screenshot/videos as a default

For some reason, Cypress:run will automatically store videos of test run. We disabled this behavior in the config as it may bloat CI/CD.

Import from your code

We use Cypress Webpack Preprocessor, to enhance Cypress build with similar options as the actual app.

We use ts-loader, with transpileOnly option to fasten build. We expect your e2e tests typing to be correct at run time.

Pure SSR testing

The cy.visitAsHtml() command allow to check the pure HTML render of a page. It will disable JS in the the page automatically.

Note: at the time of writing (2020/06) there is an open issue when needing this command in multiple tests

Loads .env.development the same way next does

We use a plugin that will in turn rely on Next.js dotenv loading capabilities. Used for instance to load the default admin user credentials in tests. As a default, it will use development values from .env.development.

Lighthouse to audit your pages

We use lighthouse to have statistics about our pages. See the main page example in scripts/lighthouse/home-stats.js. To run: run the app and use "yarn run audit"