jest-environment-jsdom-sixteen | Jest v26 ships with JSDOM @ 16 , so no reason to use | Runtime Evironment library

I am using ag-grid enterprise version in typescript react application. It works perfectly fine but when I add the below line to implement the detailed grid feature, it is throwing compilation error as mentioned below.

I'm having some difficulty running full test coverage from a script in the package.json of my create-react-app. Link to repo here;

package.json

I have been trying really hard to set the PERCY_TOKEN on a local test run according the official guideline from percy and trigger it via yarn.

The guideline says:

How to run the azure devops build completely even if there are some failing test cases. With the below mentioned scripts, the build is exiting with error code 1.

azure build pipleline tasks:

I'm using a recent version of create-react-app (in package.json, "react": "^17.0.1")

I'm trying to use react-test-library to test an app where checking checkboxes increments a counter. I've boiled down the problem to the most hello-world form I can manage. I've tried keyDown, click...

The text expects '2' and receives '0' :

Component file:

I'm trying to test a new release of an internal component library, which recently upgraded some dependencies and now uses Jest 26 internally. That library also exports some testing helpers.

In another codebase that utilizes the aforementioned component library, I'm getting the following when running certain unit tests:

I realise that this question has been asked on a number of occasions, though the environment has changed since those questions where asked: notably, JSDom now supports custom elements.

These other questions revolved around seeking alternatives (such as using Happy Dom) as JSDom did not support custom elements at that time. However, now that JSDom does support custom elements, does anyone have any information that can solve the following error?

...