If you are not on v5 yet, we recommend first following the v5 migration guide.
prefer-wait-for
was removedno-wait-for-empty-callback
was removedawait-fire-event
is now calledawait-async-events
with support for aneventModule
option withuserEvent
and/orfireEvent
await-async-events
is now enabled by default forfireEvent
in Vue and Marko shared configsawait-async-events
is now enabled by default foruserEvent
in all shared configsawait-async-query
is now calledawait-async-queries
no-await-sync-query
is now calledno-await-sync-queries
no-render-in-setup
is now calledno-render-in-lifecycle
no-await-sync-events
is now enabled by default in React, Angular, and DOM shared configsno-manual-cleanup
is now enabled by default in React and Vue shared configsno-global-regexp-flag-in-query
is now enabled by default in all shared configsno-node-access
is now enabled by default in DOM shared configno-debugging-utils
now reports all debugging utility methods by defaultno-debugging-utils
now defaults towarn
instead oferror
in all shared configs
- Removing
testing-library/prefer-wait-for
if you were referencing it manually somewhere - Removing
testing-library/no-wait-for-empty-callback
if you were referencing it manually somewhere - Renaming
testing-library/await-fire-event
totesting-library/await-async-events
if you were referencing it manually somewhere - Renaming
testing-library/await-async-query
totesting-library/await-async-queries
if you were referencing it manually somewhere - Renaming
testing-library/no-await-sync-query
totesting-library/no-await-sync-queries
if you were referencing it manually somewhere - Renaming
testing-library/no-render-in-setup
totesting-library/no-render-in-lifecycle
if you were referencing it manually somewhere - Being aware of new rules enabled or changed above in shared configs which can lead to newly reported errors