If you'd like a visual explanation, check out this video (or see the gif below):
The Karma progress reporter may indicate that the tests are taking milliseconds, but in reality, it's taking much longer...
I mentioned this on Twitter and was advised to try
Open the debug page and launch devtools to generate timings that reveal where the slowdown occurs
Here's a video demonstrating that. I'm unsure about what generating timings entails...
Occasionally, my karma tests run swiftly as expected. Other times, they're slow despite reporting milliseconds. This inconsistency occurs even when using describe.only for a few tests (though not always). It seems to happen more frequently the longer the tests have been running (the watcher).
I utilize Angular, Webpack, ES6 (with Babel), Karma, Mocha, Chai, and Sinon.
Even without the karma-webpack plugin in my test build, the issue persists when executing karma afterwards (indicating it's not related to the plugin).
The aforementioned videos depict my work project's test suite (working on coverage). However, I've encountered a similar problem with my open-source project Angular-Formly, which follows a similar testing process but is significantly smaller in terms of codebase (about 2k lines versus 30k lines).
Therefore, I would like to understand why it claims to execute quickly when it doesn't actually do so, and how can I address this speed issue?