workerIndex in event.suite.before not found
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- testing-qa
Research direction
Start by tracing the worker.on(event.suite.before) and event.dispatcher handlers, including the WorkerEmitter payload, to determine where workerIndex could be exposed. Done means event.suite.before provides the current worker index for assigning worker-specific data, with the behavior verified in the relevant test coverage.
Written by the indexing model from the issue text.
Description
What are you trying to achieve?
I want to do some specific action during event.suite.before, when worker is launched and for that, I need to get the workerIndex in the before event. But currently, it seems to be impossible.
For example, I need to assign a specific datatable to each worker.
What do you get instead?
I try two things :
use worker.on(event.suite.before) but no data is sent with WorkerEmitter
workers.on(event.suite.before, function (suite) {
console.log('--- Begin suite --');
console.log('Index du worker = ' + suite.workerIndex);
console.log('Suite = ' + suite.title);
});
use event.dispatcher but workerIndex is not found.
event.dispatcher.on(event.suite.before, function (suite) {
console.log('--- Begin workers --');
console.trace(suite);
});
I think this kind of information about current worker is very important, isn't it ?
If someone have a solution or a pullrequest to solve this, I'm interesting.
Details
- CodeceptJS version: 3.0.4
- NodeJS Version: 13.10.1
- Operating System: W10
- puppeteer
# paste config here
- 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