-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Jest open handles after upgrade from angular v12 to v13 #1426
Comments
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 |
Hi @ahnpnl Thanks for your fast response 👍 Can you please elaborate on what you think is the problem and which files you mean exactly? Regards |
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 😅 |
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. |
i created an issue in the angular/core repository. lets see if they have some insights. |
@SimonMueller Seems like you got an answer from the Angular team |
It seems that the problem is related to this library, not to Angular. |
+1 |
Currently facing the same warnings with Angular 14.2.0 and "jest-preset-angular": "^12.2.2" |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
same here with Angular "^14.1.0" and jest-preset-angular "^12.2.0" |
+1, Angular |
Version
11.1.2
Steps to reproduce
npm i
npm t
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
The text was updated successfully, but these errors were encountered: