Skip to content
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

karma fails for ng test --code-coverage without proper error message after upgrading from angular 8 to angular 11.2.4 #445

Open
gauravmasand09 opened this issue Jul 6, 2021 · 4 comments

Comments

@gauravmasand09
Copy link

My package.json below for karma
Screenshot 2021-07-06 at 09 54 10

My Error->
Screenshot 2021-07-06 at 09 58 37

Similar Error like Error thrown in afterAll [object Object]

Banging my head on this issue from the past 2 weeks, still no success.

Have recently updated Angular 8 to Angular 11.2.4.

I have total of 1000+ test cases which are failing randomly , but when runs individually it works.

Need help on this issue

@Piyush132000
Copy link

Piyush132000 commented Jul 6, 2021

Yaa same issue problem I m also facing in angular 11.2.4
Test Cases are falling randomly
No proper error message

My Error >
Screenshot from 2021-07-06 10-10-07

Truly need help with such a frustrating issue

@gauravmasand09
Copy link
Author

my test cases are failing randomly , is it the same for you @Piyush132000 ?
Screenshot 2021-07-06 at 10 28 13

@umang-goyal
Copy link

Facing the same issues. Random different test cases failing each time. Test cases are failing without any proper error unable to debug. Frustrating!!!

@Piyush132000
Copy link

my test cases are failing randomly , is it the same for you @Piyush132000 ?
Screenshot 2021-07-06 at 10 28 13

yaa, test cases are also falling the same for me I don't know why this issue coming and why test cases are failing and only 1 test case fail and it changes every time when I run ng test or ng test --no-watch --code-coverage always. it's ridiculous and frustrating.

Test cases are falling good but they are not giving a proper error message and without a proper error message how can we remove such an error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants