#react testing

Designing Effective Tests With React Testing Library
React Summit 2023React Summit 2023
151 min
Designing Effective Tests With React Testing Library
Top Content
Featured Workshop
Josh Justice
Josh Justice
React Testing Library is a great framework for React component tests because there are a lot of questions it answers for you, so you don’t need to worry about those questions. But that doesn’t mean testing is easy. There are still a lot of questions you have to figure out for yourself: How many component tests should you write vs end-to-end tests or lower-level unit tests? How can you test a certain line of code that is tricky to test? And what in the world are you supposed to do about that persistent act() warning?
In this three-hour workshop we’ll introduce React Testing Library along with a mental model for how to think about designing your component tests. This mental model will help you see how to test each bit of logic, whether or not to mock dependencies, and will help improve the design of your components. You’ll walk away with the tools, techniques, and principles you need to implement low-cost, high-value component tests.
Table of contents- The different kinds of React application tests, and where component tests fit in- A mental model for thinking about the inputs and outputs of the components you test- Options for selecting DOM elements to verify and interact with them- The value of mocks and why they shouldn’t be avoided- The challenges with asynchrony in RTL tests and how to handle them
Prerequisites- Familiarity with building applications with React- Basic experience writing automated tests with Jest or another unit testing framework- You do not need any experience with React Testing Library- Machine setup: Node LTS, Yarn
Effective Testing Strategies for React Components
Effective Testing Strategies for React Components
Article
Testing the contract of a component by focusing on inputs and outputs.Utilizing Jest mock functions for testing function props and module mocks for external modules.Implementing the React Testing Library for rendering components and simulating user interactions.Addressing asynchronous behavior in tests using the findBy query and awaiting promises.Balancing test coverage between lower-level and higher-level components.Testing React components effectively involves focusing on the contract of the component, which means understanding the inputs and outputs. This mindset helps ensure that tests are meaningful and maintainable. Instead of delving into implementation details, the aim is to test observable behavior that a user would interact with.Components have various inputs and outputs. Inputs include props, user interactions, and responses from external functions, while outputs are the rendered UI and calls to external functions. Testing begins by rendering the component and simulating user interactions to observe the outputs.Jest mock functions are essential for testing function props. They allow you to simulate and make assertions on functions passed as props. For example, if a component receives a function to handle form submission, a Jest mock function can verify that this function is called with the correct arguments.Jest module mocks are another powerful tool for handling external modules. They enable you to mock out any JavaScript module that your component depends on, ensuring that tests remain isolated from external dependencies. This is particularly useful when dealing with API calls, as it allows you to simulate responses without hitting a real server, thereby avoiding flakiness and improving test reliability.When testing asynchronous behavior, such as loading data from an API, it's crucial to handle promises correctly. The findBy query from the React Testing Library is an excellent way to wait for elements to appear on the page. It returns a promise that resolves when the element is found, allowing you to await its presence before making assertions.Organizing tests effectively involves making judgment calls about what to test at each level. Lower-level component tests focus on the detailed behavior of individual components, while higher-level tests ensure that components integrate correctly. This balance helps maintain a comprehensive test suite without excessive duplication.In addition to testing visible outputs, it's important to confirm that components make the correct external calls. This involves asserting not only on the presence of elements but also on the calls made to external functions, such as ensuring that the correct API endpoints are hit with the appropriate parameters.By focusing on the contract of a component and using tools like Jest and the React Testing Library, developers can create robust and reliable tests. This approach emphasizes testing what matters most to users and ensures that components behave as expected, both in isolation and when integrated with others.
Cypress Component Testing vs React Testing Library
TestJS Summit 2023TestJS Summit 2023
25 min
Cypress Component Testing vs React Testing Library
The Talk discusses the differences between Cypress component testing and React Testing Library (RTL). It highlights the benefits of using Cypress Component Testing, such as easier handling of complex components and a more stable testing experience in CI. The comparison between SignOn and Jest focuses on low-level spying and mocking capabilities. The comparison between Cypress Intercept and Mock Service Worker (MSW) examines their network spy and mocking capabilities. The Talk also emphasizes the superior developer experience and observability provided by Cypress component testing compared to RTL.
Integration Testing for React Native Apps
React Finland 2021React Finland 2021
25 min
Integration Testing for React Native Apps
My unpopular opinion is that testing is ... important. How do you test your React Native apps? In this presentation I will show how to run full integrations tests using Cypress while the RN app is running in the browser. This method can cover most of the application's code and be effective at finding logical errors and mistakes when calling the server APIs.