End-to-end (E2E) testing verifies application flow from start to finish. Instead of manual testing, continuous integration (CI) automates this process. Write code, save it, and let the tools ensure it doesn't break existing functionality. Cypress is a powerful E2E testing framework that simplifies this process, particularly for modern JavaScript libraries like React.
Setting up a Test Application
This tutorial uses a sample todo application. Clone the repository to follow along:
git clone [email?protected]:kinsomicrote/cypress-react-tutorial.git
Navigate to the directory and install dependencies:
cd cypress-react-tutorial yarn install
Install Cypress:
yarn add cypress --dev
Open Cypress:
node_modules/.bin/cypress open
For easier access, add this script to package.json
:
"scripts": { "cypress": "cypress open" }
Now run yarn cypress
to open Cypress. Start the React app with yarn start
to see the application.
Let's create a basic test in cypress/integration/init.spec.js
:
describe('Cypress', () => { it('is working', () => { expect(true).to.equal(true); }); });
This confirms Cypress is working. Now, let's test visiting the app:
it('visits the app', () => { cy.visit('http://localhost:3000'); });
To avoid repeating the URL, set a base URL in cypress.json
:
{ "baseUrl": "http://localhost:3000" }
The test can now be simplified to:
it('visits the app', () => { cy.visit('/'); });
Testing Form Controls and Inputs
Create cypress/integration/form.spec.js
to test user interaction.
describe('Form', () => { beforeEach(() => { cy.visit('/'); }); it('focuses the input', () => { cy.focused().should('have.class', 'form-control'); }); it('accepts input', () => { const input = "Learn about Cypress"; cy.get('.form-control') .type(input) .should('have.value', input); }); it('displays list of todos', () => { cy.get('li').should('have.length', 2); }); it('adds a new todo', () => { const input = "Learn about Cypress"; cy.get('.form-control') .type(input) .type('{enter}') .get('li') .should('have.length', 3); }); it('deletes a todo', () => { cy.get('li') .first() .find('.btn-danger') .click() .get('li') .should('have.length', 1); }); it('deletes all todos', () => { cy.get('li') .first() .find('.btn-danger') .click() .get('li') .first() .find('.btn-danger') .click() .get('.no-task') .should('have.text', 'All of your tasks are complete. Nicely done!'); }); });
These tests cover input focus, input acceptance, initial todo count, adding a new todo, deleting a single todo, and deleting all todos.
Testing Network Requests
Testing network requests ensures data fetching works correctly. For example, using the JSON Placeholder API:
describe('Request', () => { it('displays random users from API', () => { cy.request('https://jsonplaceholder.typicode.com/users') .should((response) => { expect(response.status).to.eq(200); expect(response.body).to.have.length(10); expect(response).to.have.property('headers'); expect(response).to.have.property('duration'); }); }); });
This verifies the API response status, data length, and response properties.
Running Tests from the Command Line
Run Cypress tests from the terminal:
npx cypress run
To run specific tests:
npx cypress run --spec "cypress/integration/form.spec.js"
This provides a command-line summary of the test results. Refer to the Cypress documentation for more advanced command-line options.
Conclusion
Cypress simplifies E2E testing, making it accessible and beneficial for developers. This tutorial demonstrates basic to intermediate testing techniques, encouraging you to explore its capabilities further. Remember to consult the Cypress documentation for more advanced features and best practices.
The above is the detailed content of Using Cypress to Write Tests for a React Application. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
