run-multiple execution creates output sub folders with alphanumeric value instead of browser names
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- testing
Research direction
Start by reproducing run-multiple execution with Chrome, Safari, Firefox, and Edge, then trace the output subfolder naming entry point. Confirm that folders use browser or channel names such as parallel_Chrome_1 rather than alphanumeric values, and validate the result with the download and FileSystem helper scenario described in the issue.
Written by the indexing model from the issue text.
Description
What are you trying to achieve?
For run-multiple execution with multiple browsers like Chrome, Safari, Firefox and Edge, the subfolder in the output folder should have a name like parallel_Chrome_1, parallel_Safari_2, parallel_Firefox_3 etc
What do you get instead?
While executing using run-multiple the subfolder in the output folder should have name like the following:
parallel_0096a0c740a073d21e23267bf167f711a9826c9d84addc417bc5b320df11e0bd_1
parallel_f7899c9a407a947a824a4955416619aef2c53bd0fbb18965b53d0a3fb4c207d6_2
instead of browser/channel name some alphanumeric value is present in the folder name.
This makes it difficult to do many validations. For eg:
Validating the file download using handleDownloads and FileSystem helper, like using methods I.amInPath('output/folderName');
where folderName is parallel_0096a0c740a073d21e23267bf167f711a9826c9d84addc417bc5b320df11e0bd_1.
This is only 1 example
Provide console output if related. Use
--verbosemode for more details.
# paste output here
Provide test source code if related
// paste test
Details
- CodeceptJS version: 3.5.15
- NodeJS Version: 20
- Operating System: Mac OS
- Playwright (if related)
- Configuration file:
# 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