does not play well with jest 27

[TrejGun]

• @testing-library/react version:

"@testing-library/jest-dom": "5.12.0",
"@testing-library/react": "11.2.7",

• Testing Framework and version:

"jest": "27.0.1",

• DOM Environment:

jsdom

Relevant code or config:

please refer to this project
https://github.com/TrejGun/casino

What you did:

updated jest from 26 to 27

What happened:

Tests are now failing with

    ReferenceError: clearImmediate is not defined

Reproduction:

see above

Problem description:

Tests are failing :(

Suggested solution:

N/A

[ediblecode]

@TrejGun it looks like this was a breaking change in Jest 27, see https://github.com/facebook/jest/blob/master/CHANGELOG.md#fixes-2. Specifically:

[jest-environment-jsdom] [BREAKING] Remove Node globals setImmediate and clearImmediate #11222

See also testing-library/dom-testing-library#914 which looks related.

[andrevenancio]

With RTL:

"@testing-library/dom": "^7.30.0",
"@testing-library/jest-dom": "^5.11.9",
"@testing-library/react": "^11.2.5",
"@testing-library/user-event": "^13.0.10",

And Jest version 27.0.1

I'm getting TypeError: Cannot destructure property 'AsymmetricMatcher' of '_prettyFormat.default.plugins' as it is undefined.

[tdeekens]

Seeing the same problems. Will be even be possible for rtl to work in v26 and v27 of Jest with the same version?

[dodoongtak]

[Date: 2 June 2021]

with RTL:

//dev dep
"@testing-library/jest-dom": "^5.12.0",
"@testing-library/react": "^11.2.7",
"jest": "^27.0.3",

//dep
"react": "^17.0.2",

After updating jest version: 26 -> 27

Following Error Message Prompts out.

The error below may be caused by using the wrong test environment. See https://jestjs.io/docs/configuration#testenvironment-string.

Consider using the "jsdom" test environment.

ReferenceError: document is not defined

---

As I've looked over the PRs mentioned this issue,

@kentcdodds has already recognized the issue regarding the jest27 updates on switching default test env from jsdom to node.
Discussion here: kentcdodds/kcd-scripts#210

Applause for @eps1lon 👏👏👏

---

Unfortunately, I could not clearly figure out the future action plan to resolve this breaking change of jest.

1. Would it be switching to node as default test env in testing-library?

Or

2. As mentioned in the jest blog post regarding 27update, we still can configure testEnvironment as jsdom instead of node.

Would it be still using jsdom though they suggest node?

FYI:
The flipping default - Breaking Change started from jestjs/jest#9874

[m4thieulavoie]

Having the same issue after upgrading to Jest@27. Is anyone working on a fix?

[eps1lon]

Having the same issue after upgrading to Jest@27. Is anyone working on a fix?

We're in the process of fixing this in @testing-library/dom. This particular issue should already be fixed in the alpha but it'll take some time to test it before we can release a new major of @testing-library/react.

[jRichardeau]

Hello,

Facing same issue but it seems to work for @testing-library/dom < 7.29.6, so when forcing the 7.29.5 version in the dependencies of my package.json it solved my problem.

[marybeshaw]

We have the same issue. Trying to update a monorepo with 297 test suites to jest v27 caused a full 47 test suites to fail. A couple of issues I saw:

• Something is wrong with promise cleanup. A test of code that relied on .finally() timed out and never finished.
• Something is wrong with timers, both real and fake. It's possible this is just another symptom of the promise cleanup issue.
• Clearing a mocked Date.now (created using jest.spyOn) failed (Date.now.mockClear() threw an error that mockClear wasn't a function).
• New messages:ReferenceError: You are trying to access a property or method of the Jest environment after it has been torn down.. These are probably leaks I could fix if I could figure out which test was being torn down.

Jest 27 config file changes I made:

  testEnvironment: 'jsdom',
  timers: 'legacy',
  testRunner: 'jasmine2',

[tdeekens]

Same issues here but also not only rtl related.

1. Promises: native Promises (not polyfilled) do not seem to be controlable by Jest v27 making tests fail
2. Timers: the internal change to use sinon (in v27) seems to have the impact of jest not being able to control time when using core-js (it does overwrite some thing)

It turned out that disabling core-js under test for us was generally a good idea. However, leaving us with the issue that jest v27 seems to struggle with native promises.