Course Introduction

Introduction

Introduction to module 1 - Plugin features and set up

Intro to module 1

Main features and options

In this course we won't be building an app from scratch, but fixing existing examples and apps containing errors. We need to download and setup the provided sample codes to be able to work with them in the corresponding lessons.

Working with the provided sample codes

Get instant feedback by setting ESLint in your code editor

Integrating ESLint into your code editor

Install and configure eslint-plugin-testing-library in your codebase

Setting the plugin up in your project

The advanced config to lint only what's necessary

Run the plugin only on test files

Guidelines to migrate from a previous version to the latest v5

Migrating the plugin to v5

How to take advantage of the plugin when working in a Create React App project

Using the plugin in a Create React App project

Plugin features and set up

Introduction to module 2 - Rules for following best practices

Intro to module 2

Understanding the errors reported by the rule `no-manual-cleanup`

no-manual-cleanup rule

Understanding the errors reported by the rule `prefer-screen-queries`

prefer-screen-queries rule

Understanding the errors reported by the rule `no-await-sync-query`

no-await-sync-query rule

Rules for following best practices

Rules for preventing errors

Rules for style guidelines & Advanced Features

Testing Library is a great bunch of utils to write tests for your UI. It has become the favorite testing choice of many users since it encourages you to write more maintainable and reliable tests, encourages best practices, and doesn't focus on implementation but behavior.

However, testing your app correctly with Testing Library is not always straightforward. _What query variant fits better for this situation? How should I check appearance/disappearance? What is the best way to handle async behaviors? Why am I seeing this particular error or warning? Why am I not getting the expected element?_ These are very typical questions while writing tests with Testing Library.

You are not alone! This course aims to help you master these situations with the assistance of `eslint-plugin-testing-library`: the official ESLint plugin for Testing Library.

The course will boost your Testing Library skills by using this plugin
as a companion when writing tests. You will get instant feedback by linting your tests code, so you can **follow best practices and anticipate common mistakes for Testing Library**, as well as better understand its utils and their main purposes.

Get ready to say goodbye to flaky tests!

Master writing Testing Library tests with eslint-plugin-testing-library by anticipating common mistakes and following best practices

Master Testing Library with ESLint Plugin

How to set up eslint-plugin-testing-library in your codebase

Getting ESLint feedback directly in your code editor and your terminal

ESLint advanced config for getting more granular control over the linting process

Better understanding of Testing Library errors

Following best practices for Testing Library tests

During this module, we will see all the rules under the "Best Practices" category.

---
title: Intro to module 2
description: Introduction to module 2 - Rules for following best practices
role: 'INTRODUCTION'
isPublicLesson: false
privateVideoUrl: https://fullstack.wistia.com/medias/c0tk5pukdd
---

# Introduction

During this module, we will see all the rules under the "Best Practices" category.

There are situations where you can implement something with Testing Library in several ways. However, some of them offer some advantages over the rest, are more maintainable, or generate more understandable errors when failing. Rules in this group will suggest you switch your code to the recommended way.

Mario Beltrán Alarcón

This is the first model where we will see errors reported by easily implagging

In the lessons of this model, we will cover all the rules under the best

There are situations where you can implement something with tested leverage in

However, some of them offer some advantages over the rest.

Are more maintainable or generate more understandable errors when failing.

Rules in this group will suggest you switching your code to the recommended way

The rules included in this category are this.