chore(deps): update testing library (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/dom	^7.31.2 -> ^8.5.0
@testing-library/react	^11.2.7 -> ^12.1.0
@testing-library/react	^9.5.0 -> ^12.1.0

---

Release Notes

testing-library/dom-testing-library

v8.5.0

Compare Source

Features

• config: Add unstable_advanceTimersWrapper (#​1022) (45830f5)

v8.4.0

Compare Source

Bug Fixes

• Use syntax compatible with older TypeScript versions (#​1026) (8311c8d)

Features

• Add element type generic argument to queries (#​1023) (f55f19b)

v8.3.0

Compare Source

Features

• restore prettyDOM logging for Cypress (#​1018) (460115a)

v8.2.0

Compare Source

Features

• ByRole: Allow filter by aria-current state (#​943) (fbbb29a)

v8.1.1

Compare Source

Bug Fixes

• support getting text of inputs of type reset (#​1011) (54b9a5f)

v8.1.0

Compare Source

Features

• fireEvent: Add resize event (#​990) (75197fe)

v8.0.0

Compare Source

Recommendations

1. If you're using jest fake timers make sure you use modern timers
   jest 27:

   -jest.useFakeTimers('legacy')
   +jest.useFakeTimers('modern')
    // jest.config.js
   -"timers": "legacy",
   +"timers": "modern",

   jest 26:

   -jest.useFakeTimers()
   +jest.useFakeTimers('modern')
    // jest.config.js
   -"timers": "legacy",
   +"timers": "modern",

chore

• Release v8 as stable (#​979) (d347302)

BREAKING CHANGES

• Remove deprecated waitFormDOMChange
• Remove deprecated waitForElement
• The timeout in waitFor(callback, { interval, timeout } ) now uses the same clock as interval. Previously timeout was always using the real clock while interval was using the global clock which could've been mocked out. For the old behavior I'd recommend waitFor(callback, { interval, timeout: Number.POSITIVE_INFINITY }) and rely on your test runner to timeout considering real timers.
• <script />, <style /> and comment nodes are now ignored by default in prettyDOM .If you whish to return to the old behavior, use a custom filterNode function. In this case prettyDOM(element, { filterNode: () => true }).
• node 10 is no longer supported. It reached its end-of-life on 30.04.2021.

testing-library/react-testing-library

v12.1.0

Compare Source

Features

• improve JSDocs for RenderOptions (#​909) (fbacb0d)

v12.0.0

Compare Source

Bug Fixes

• Bump testing-library/dom to v8 alpha (#​923) (770246e)
• Update @​testing-library/dom (#​931) (05c7421)

Features

• Bump @​testing-library/dom (6e6bf85)
• Drop support for node 10 (#​930) (42dad78)

BREAKING CHANGES

• Bump @testing-library/dom to 8.0.0. Please check out the @testing-library/[email protected] release page for a detailed list of breaking changes.
• node 10 is no longer supported. It reached its end-of-life on 30.04.2021.

---

Configuration

📅 Schedule: "before 7am on the first day of the month" in timezone GMT.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[LekoArts]

Had to switch testing-library/react to v11 due to some bugs with fakeTimers:

• findBy* no longer waiting when used with jest fake timers testing-library/dom-testing-library#988
• jest.useFakeTimers are not working after update to version 8 testing-library/dom-testing-library#1007
• Allow fake timers other than jest testing-library/dom-testing-library#987