Repository navigation
Slow test execution start on local #5692
Replies: 1 comment
|
The "slow once, fast again immediately, then slow again after some idle time" pattern makes me suspect the startup layer rather than the test itself. I would isolate it in this order. First, bypass .\node_modules.bin\codeceptjs.cmd run --steps --grep "..." If that is consistently fast while: npx codeceptjs run --steps --grep "..." is slow, the delay is in npm/npx resolution rather than CodeceptJS. If both are slow, try a command that initializes CodeceptJS but does not start the browser/tests, and time that separately. If the delay still happens before CodeceptJS prints its normal startup output, check Windows Defender / endpoint security scanning of the project and I would not disable Defender globally. As a diagnostic, temporarily test with the project directory excluded (if your environment allows it) and compare timings. Also compare Node 24 with the current Node LTS supported by your project. If the issue disappears on LTS, that gives you a useful reproduction point. In short:
The fact that |
Uh oh!
There was an error while loading. Please reload this page.
I've recently started noticing very slow execution when running tests with npx codeceptjs run --steps --grep.
If I rerun immediately after a slow run, it's faster — but if I wait a few minutes and run again, it starts slow again. I also tried running with --verbose, but there's nothing meaningful logged before actual execution starts.
Environment:
Node: 24.16.0
OS: Windows 11 10.0.26200
CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12950HX
Chrome: Not Found
Edge: Chromium (151.0.4129.93)
Firefox: undefined
Safari: N/A
All reactions