Let's understand the testing syntax by providing metaphors and referring to real life. We'll understand the concepts of testing.
It will be difficult for a computer to understand plain text, so we need to convert our grouped tests into something that a computer can understand.
Converting the syntax
Let's convert one of the features created earlier. Typically, most testing tools use blocks describe and it to describe tests. Describe means functionality, and it means a specific test. We will make the following transformation:
Note that we have moved from questions to assertions. The reason is simple - less text is produced and it is more intuitive to read. Also, if it is possible to simplify an assertion to a shorter form, it is worth doing (see Pizza plate is clean).
We know how to communicate with the computer and show him how to mark our tests. However, we still have some things to understand before we write implementations for our tests.
If you enjoyed it, be sure to visit us on Linkedin where we regularly upload content from programming.
- 1. Basics
Grouping the tests
The usage of describe and it
The best practices for naming tests
Navigating the different types of software tests
- 2. Mastering unit testing
Project and tests setup
Unit tests review
React component testing
Snapshot testing in React
Understanding stubs in testing
Understanding mocks in testing
Creating testing fixtures
Using spies in React and Typescript
Mocking environment variables
Using dependency injection pattern to improve fixtures
- 3. Mastering integration testing
Understanding the integration tests
Using MSW library to remove implementation details from tests
Creating fixture for MSW to reduce boilerplate and setup
- 4. Mastering e2e tests