Long start up period in case of too many testcases
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- performance, testing
Research direction
Start by reproducing the delay with yarn codeceptjs run --steps --verbose --grep=@debug using the reported large feature set. Read node_modules/codeceptjs/lib/mochaFactory.js and the referenced mocha.loadFiles path to identify where startup time is spent. Done means the initial pause is substantially reduced for many test files without changing scenario execution.
Written by the indexing model from the issue text.
Description
What are you trying to achieve?
Pause between codeceptjs run command and first scenario steps execution should not spend seconds, tens of seconds
What do you get instead?
In the case with a lot of test files and scenarios into these files I see initial delay in ~40 seconds . Related with ~70 feature.ts files and ~400 scenarios.
Who knows, it can be related with initial reading of files with tests and can be related with node_modules/codeceptjs/lib/mochaFactory.js and mocha.loadFiles...
In case of project with small count of files and scenarios delay < 2-3 seconds.
Provide console output if related. Use
--verbosemode for more details.
make test-e2e GREP=@debug
yarn codeceptjs run --steps --verbose --grep=@debug
yarn run v1.22.10
$ XXX/node_modules/.bin/codeceptjs run --steps --verbose --grep=@debug
{
startUrl: 'http://localhost:9000',
tests: 'XXXX/**/*.feature.ts'
}
Details
- CodeceptJS version: 2.6.11/3.0.4
- NodeJS Version: v12.19.0
- Operating System: MacOS 10.15.7
- puppeteer
- Dominant language
- JavaScript
- Stars
- 4.2k
- Forks
- 756
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codeceptjs/CodeceptJS
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
codeceptjs/CodeceptJS#5420 · 1 comment ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
codeceptjs/CodeceptJS#5358 · 1 comment ·
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
codeceptjs/CodeceptJS#4958 · 10 comments · 2 reactions ·
-
stale
Difficulty 1/5 Under an hour Newbie friendliness 72/100
codeceptjs/CodeceptJS#4778 · 3 comments ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 38/100
codeceptjs/CodeceptJS#5618 · 1 comment ·
All issues in codeceptjs/CodeceptJS
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dream-num/dsh-univer-office#104 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
avniproject/avni-webapp#1811 ·
-
area/auroraboot area/webui bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100