[Bug]: Jest open handles after upgrade from angular v12 to v13

[SimonMueller]

Version

11.1.2

Steps to reproduce

1. Clone https://github.com/SimonMueller/jest-preset-angular-open-handle-reproduction
2. Run npm i
3. Run npm t
4. See test output

Expected behavior

No open handles after tests are done executing.

Actual behavior

Two open handles after tests are done executing. See screenshot:

Additional context

We saw this behavior after upgrading from angular 12 where these open handles are not present. I tested this aswell with the repo above.

Environment

System:
    OS: Linux 5.15 Ubuntu 22.04 LTS 22.04 (Jammy Jellyfish)
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 14.19.1 - ~/.nvm/versions/node/v14.19.1/bin/node
    npm: 6.14.16 - ~/.nvm/versions/node/v14.19.1/bin/npm
  npmPackages:
    jest: 27.5.1 => 27.5.1

[ahnpnl]

Not sure if we can do anything in this case. This is the only way to set up test environment to work with Angular. You can also copy the file content and put it in your own setupJest.ts. The file is just a convenient way for users to use.

[SimonMueller]

Hi @ahnpnl

Thanks for your fast response 👍

Can you please elaborate on what you think is the problem and which files you mean exactly?
So is this a known issue / bug?

Regards

[ahnpnl]

The file is here https://github.com/thymikee/jest-preset-angular/blob/main/src/config/setup-jest.ts

i think this is an existing issue already as I saw this in the past as well. Idk what the problem can be tbh. I never check this 😅

[SimonMueller]

So you think the problem is with angular v13?

What i find special is that it is only after the upgrade from angular v12 to v13 and i have never seen it before since angular v11.

We had some failing tests where this seems to be the cause which is not really nice for us. And as we can reproduce it with such a simple example i think it would be good to have a look at it.

[ahnpnl]

seem like this is the issue. It comes from getTestBed

[SimonMueller]

i created an issue in the angular/core repository. lets see if they have some insights.

[marvincayetano]

@SimonMueller Seems like you got an answer from the Angular team
Andrew from angular tried fixing this bug.

AndrewKushnir solution

[borjapazr]

It seems that the problem is related to this library, not to Angular.

angular/angular#45776 (comment)

[Bil0]

Hello, same error with angular v14

[cangomescisco]

+1

[MaximeKoitsalu]

Currently facing the same warnings with Angular 14.2.0 and "jest-preset-angular": "^12.2.2"

[JamesODonoghue]

+1

[adoroshenko-lohika-tix]

+1

[ialterovych-lohika-tix]

+1

[estrudels]

+1

[georgevbm]

+1

[rajeshkumaravel]

+1

[leobrines]

same here with Angular "^14.1.0" and jest-preset-angular "^12.2.0"

[jseashell]

+1, Angular ^13.2.3 and jest-preset-angular ^11.1.2