What complex code is not easy to debug every developer knows. But not all developers know how to use the power of automated testing to verify the application behavior. Therefore, in this article, I will show you how to avoid wasting a lot of time trying to find UI bugs and also making sure that the program works as expected.
“The more your tests resemble the way your software is used, the more confidence they can give you.” - Kent C. Dodds, creator of React Testing Library
Testing has become a major requirement for React projects today. And this is because this technique gives the team more confidence and helps to release the project quickly, since the code is more reliable.
Jest and React Testing Library are two tools that help us a lot to create tests for our React components. If you don’t know what I am talking about or if you want to learn more about it, stay with me. 😁✨
Although front-end testing is growing with React's popularity, I don't see it as a trend, but as a part that should be mandatory in any type of project that involves end user interaction coding.
- Helps us to detect bugs earlier
- Provides us with our own documentation on the code
- Forces us to write better code when building small components with single responsibility
- Ensures the code will be more consistent across the team
- Gives us more confidence because it makes the application easy to maintain, allowing developers to safely refactor the code
- Unit testing: is used to validate the operation of the smallest code units in the system. The idea is that this type of test needs to be simple and without any dependence on external functionality - of course, there are some exceptions where the component needs to work with data from the database or some other source, in which case we use mock (let's see more about that later).
- Functional testing: checks if multiple units work together.
Let's imagine a search field that, when clicked, expands. When typing something, a suggestion box is shown with data from an API; and if there are no suggestions, a feedback message is displayed.
Unit tests can be: check if the search field will expand when receiving focus; check if, when typing something, the API fetch method is called; check if there are no suggestions, a feedback message displayed…
Function tests can be: user simulation by clicking, typing, deleting...
There is a good practice called test-driven development (TDD) that is used to ensure that our tests will cover all the functionality that the component must have before creating the component itself. In this way, we guarantee that the code will be agnostic, that is, everything has to work regardless of how the code was implemented.
Basically the process is:
- Red ❌: First, we need to create all the tests and they all failed
- Green ✔️: We then provide a simple solution for all tests to pass
- Refactor ♻️: And finally, we refactor the solution in the best possible way
Why is it important having tests done before the component's code?
If the tests are created last, we tend to write the tests according to the code that was implemented, instead of the problem that must be solved. That is, the test can be oriented towards implementation instead of functionality, which can be a problem if the solution/implementation changes in the future. Read more about TDD here.
In this article, we will focus on two of these testing tools that are very successful in the React community and which I am a huge fan of: jest and react testing library.
Jest is a test runner that executes many tasks by using a few functionalities. If you already worked with Gulp you can imagine something similar when we refer to jest but much easier to configure and focused on testing.
- Easy to understand and use
- Zero configuration (or just a minimum necessary)
- Well documented
- Snapshot testing to prevent accidental UI changes
- Mocking function to work with fake data that must be provided by a database or other source
- Extensible framework - we can integrate other tools to work with it
- Fast and performance-focused - tests run in parallel
- Code coverage information to ensure that all code is being tested.
“React Testing Library is a set of helpers that let you test React components without relying on their implementation details.” - React team
You can test the UI of React components just using the Jest testing framework, of course, but React Test Library (RTL) provides extra lightweight utility functions for Jest to work with React components, saving your time and encouraging best testing practices - it forces your application to be more accessible.
If you've worked with Enzyme (another test library created by AirBnb), you can probably imagine the benefits of RTL. The difference is that RTL is more modern and powerful to handle the graphical user interface: render the component, select it using the aria-label attribute and check its color, for example.
- RTL encourages us to write better components through accessibility approaches
- Focus on how components look and behave in the DOM instead of props and states
- Great integration with Jest
RTL is awesome, we can create tests based on DOM elements using several different queries, then create a snapshot of the component to prevent any unexpected user interface changes. Therefore, whenever the running test identifies any changes, the tests will fail. Thus, you can make the decision to update the snapshot or correct your code so that no differences are found. In addition, we can also use events to simulate user interactions: such as clicks and form fills, for example. Isn’t it awesome?
Watch the tutorial video below to better understand the React Testing Library through practical examples
RTL is built on top of DOM Testing Library that has specific libraries to work with many kinds of framework.
Jest Styled Components is a dependency of Jest with a set of utilities for testing Styled Components: media-queries, theme…
When using tests in React, we can be sure that the user interface code will do what we expect, focusing on functionality first (TDD) and ensuring better accessibility.
I realize that many developers and companies see testing as just a lovely idea. But I think we need to stop wasting time on debugging and take advantage of testing to gain more confidence, keep the code consistent across the team, and improve our code by following best practices and conventions. ✌😁✨
Leave in the comments if you have used these testing tools or if you are using a different approach to apply tests to React projects. Until the next! 👋
Please give this post a 💓, 🦄, or 🔖 if it you learned something!