Skip to content

Latest commit

 

History

History
30 lines (25 loc) · 2.03 KB

File metadata and controls

30 lines (25 loc) · 2.03 KB

Guide: migrating to v6

If you are not on v5 yet, we recommend first following the v5 migration guide.

Overview

  • prefer-wait-for was removed
  • no-wait-for-empty-callback was removed
  • await-fire-event is now called await-async-events with support for an eventModule option with userEvent and/or fireEvent
  • await-async-events is now enabled by default for fireEvent in Vue and Marko shared configs
  • await-async-events is now enabled by default for userEvent in all shared configs
  • await-async-query is now called await-async-queries
  • no-await-sync-query is now called no-await-sync-queries
  • no-render-in-setup is now called no-render-in-lifecycle
  • no-await-sync-events is now enabled by default in React, Angular, and DOM shared configs
  • no-manual-cleanup is now enabled by default in React and Vue shared configs
  • no-global-regexp-flag-in-query is now enabled by default in all shared configs
  • no-node-access is now enabled by default in DOM shared config
  • no-debugging-utils now reports all debugging utility methods by default
  • no-debugging-utils now defaults to warn instead of error in all shared configs

Steps to upgrade

  • 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 to testing-library/await-async-events if you were referencing it manually somewhere
  • Renaming testing-library/await-async-query to testing-library/await-async-queries if you were referencing it manually somewhere
  • Renaming testing-library/no-await-sync-query to testing-library/no-await-sync-queries if you were referencing it manually somewhere
  • Renaming testing-library/no-render-in-setup to testing-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