feat: parallel execution by workers on multiple browsers results with multiple output folders #3971
Conversation
lib/workers.js
Outdated
| collection.createRuns(selectedRuns, config).forEach((worker) => { | ||
| const _config = { ...config }; | ||
| _config.output = `${currentOutputFolder}/${worker.config.browser.browser}`; |
There was a problem hiding this comment.
Maybe ${worker.name} is better than ${worker.config.browser.browser}
Then an output folder name will be e.g. personal:chromium1 (or dev:chromium1) instead of chromium and it's more similar to naming when using run-multiple mode.
The run-multiple mode uses personal_chromium_1 (<profile>_<browser_name>_<browser_order>)
There was a problem hiding this comment.
Could you help tell what worker.name returns?
There was a problem hiding this comment.
I run a test in VSCode in debug mode and just saw the value. I guess "worker.name" returns <profile_name>:<browser_name>1.
Not sure for 1 means. I thought that it's a worker ID, but in my testing it's always 1 even for multiple workers (e.g. 2 workers).
There was a problem hiding this comment.
Thanks for your reply!
There was a problem hiding this comment.
Yes, folder name is e.g. dev_firefox1 (profile "dev", browser "firefox") after the latest fixes 鉁旓笍 .
Also XML report result.xml is stored to a folder per browser 鉁旓笍 .
kobenguyent
deleted the
3970-feature-request-parallel-execution-by-workers-on-multiple-browsers-results-with-multiple-output-folders
branch
Motivation/Description of the PR
Type of change
Checklist:
npm run docs)npm run lint)npm test)