We'll check how we can group the test cases to avoid problems with readability and understanding their context.
You know very well how grouping and categorization allows us to better find ourselves in the reality around us. It is the same with tests, which we group into functionalities.
Let's group the tests
It's time to look at the tests from a broader perspective. In everyday life, we don't deal solely with teaching a colleague how to make a pizza. We can teach him other things like: cutting with a knife, cooking pasta, driving a car. Each of these topics will have different questions and answers (our tests).
So let's group our functionalities and write the appropriate questions for them.
You already know what the tests are and how to group them.
You need to group your tests. Without that they will be hard to maintain and their context will be blurry.
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