Skip to content

Latest commit

 

History

History
58 lines (37 loc) · 3.52 KB

README.md

File metadata and controls

58 lines (37 loc) · 3.52 KB

integration-tests

Example forked from sarahatwork/integration-tests described in React Integration Testing: Greater Coverage, Fewer Tests that shows component testing using Cypress and cypress-react-unit-test.

Read My Vision for Component Tests in Cypress

Specs

All Cypress specs are in src/**/*cy-spec.js and follow Jest + RTL unit tests. But after mount(...) they become full web applications and you can interact with the test via standard Cypress commands.

LoginModule tests

// src/LoginModule/index.cy-spec.js
mount(<LoginModule />);

// it renders empty email and password fields
cy.get('input#email').should('have.value', '')
cy.get('input#password').should('have.value', '')

// it renders enabled submit button
cy.contains('button', 'Submit').should('be.enabled')
Jest + RTL Cypress Description
useLogin.unit.test.js useLogin.cy-spec.js Testing React Hook
Login.unit.test.js Login.cy-spec.js Testing <Login> component
LoginForm.unit.test.js LoginForm.cy-spec.js Testing <LoginForm> component
index.unit.test.js - See "Note 1" below
index.integration.test.js index.cy-spec.js Top level component test
- cy-spec.js Full end-to-end Cypress test against localhost:3000

Bonus: the LoginModule tests can be executed as a full end-to-end test, see cypress/integration/cy-spec.js. Just use cy.visit instead of mount, but the rest stays the same:

E2E test

Bonus 2: component tests using cypress-react-unit-test collect code coverage by default. For E2E test we instrument the application on the fly using @cypress/instrument-cra, see How to instrument react-scripts web application for code coverage.

A single E2E test covers 100% of the source code. Component tests together also cover 100% of the code.

Coverage report

Bonus 3: if you like testing-library/react, there is testing-library/cypress that you can use in both component and e2e tests

Note 1: there is a Jest test that uses a snapshot. While there are Cypress snapshot plugins, I would rather use Visual testing. All Cypress plugins should work in both E2E and component tests.

Debugging

If code coverage is missing, look at the debug logs from the instrumentation, code coverage and component testing modules. Set the following environment variable DEBUG and run the code

DEBUG=instrument-cra,cypress-react-unit-test,code-coverage yarn dev

When running component test, you should also be able to see window.__coverage__ object in the context of the app frame

Window coverage