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

---
title: Migrating the plugin to v5
description: Guidelines to migrate from a previous version to the latest v5
isPublicLesson: true
privateVideoUrl: https://fullstack.wistia.com/medias/jxx3j1pj33
---

# Migrating the plugin to v5

If you are already familiar with the `eslint-plugin-testing-library` but you are still using v3 or v4 of the plugin: this lesson will be helpful for you. Otherwise, you can skip it since we are going to see how to migrate to v5.

Version 3 of the plugin is probably the most famous one since it was included in Create React App v4. Since this version, two new majors have been released but there are people still migrating to the most recent one. In this lesson, we are going through the changes on v4 and v5, and how to update to the latest.

## From v3 to v4

### Features

This is the list of features and rules introduced in V4:

-   New rules:

    -   `no-container`
    -   `no-wait-for-multiple-assertions`
    -   `no-node-access`
    -   `no-promise-in-fire-event`
    -   `no-wait-for-side-effects`
    -   `prefer-user-event`
    -   `render-result-naming-convention`
-   Detection of Testing Library utils improved and more consistent across the whole plugin
-   Aggressive Reporting mechanism
-   Shared Settings
-   Tons of errors fixed and internal validations added

### Breaking changes

This is the list of changes that may break your current setup after upgrading to v4:

-   Minimum ESLint version required is 7.5 now
-   `recommended` preset has been renamed to `dom`
-   `no-promise-in-fire-event` rule enabled in dom, angular, react and vue Shareable Configs
-   `no-wait-for-empty-callback` rule enabled in dom, angular, react and vue Shareable Configs
-   `prefer-screen-queries` rule enabled in dom, angular, react and vue Shareable Configs
-   `no-container` rule enabled in angular, react and vue Shareable Configs
-   `no-node-access` rule enabled in angular, react and vue Shareable Configs
-   `render-result-naming-convention` rule enabled in angular, react and vue Shareable Configs
-   `no-debug` rule changed from "warning" to "error" in angular, react, and vue Shareable Configs
-   `renderFunctions` option has been removed from `no-debug` and `no-render-in-setup` in favor of Aggressive Reporting feature
-   `customQueryNames` option has been removed from `prefer-explicit-assert` in favor of the Aggressive Reporting feature

Guidelines to migrate from a previous version to the latest v5