You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test run time can differ by more than an order of magnitude.
Other details that might be useful
I was running ~200 tests (30 of them were component tests). Execution time was either ~0.7s or ~20s and the test runner would eventually crash. Turns out the slow and unstable tests were a result of chrome being out of focus. Chrome windows that are out of focus get throttled.
Looking through the rebuild speed thread, #1980, I noticed some complaints about ng test test speed. Specifically this comment. I'd like to suggest including a tip in ReadMe to keep chrome in focus. Since this is quite a hard to diagnose issue I think it will be very helpful.
Activity
filipesilva commentedon Dec 12, 2016
The problem with
ng testin that thread was mostly fixed by #2840, because at the time code coverage was always being added.A comment like this would be nice, even though there isn't anything else we can do. Would you be interested in adding it?
antonybudianto7 commentedon May 3, 2017
no blueprint update after https://github.com/angular/angular/pull/16250/files ? @filipesilva
filipesilva commentedon May 22, 2017
Newer karma-chrome-launcher versions fix this automatically.
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.