Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Not able to do file download validation with run-multiple execution

Open
#4,273 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
testing

Research direction

Start by tracing the run-multiple execution entry point and the handleDownloads and FileSystem helper methods mentioned in the report. Reproduce the case with multiple browsers and parallel_output directories; done means file-download validation accepts the generated output path rather than requiring a fixed folder name.

Written by the indexing model from the issue text.

Description

stale
What are you trying to achieve?

Validating the file download using handleDownloads and FileSystem helper, like using methods I.amInPath('output/folderName');
with run-multiple execution with multiple browsers like Chrome, Safari, Firefox and Edge, and check whether file is there in the subfolder in the output folder parallel_output_1, parallel_output_2, parallel_output_3 etc

What do you get instead?

Not able to use the dynamic path in the method I.amInPath('output/folderName')
Tried this way I.amInPath('output/parallel_output_*') but not working

Provide console output if related. Use --verbose mode for more details.

# paste output here

Provide test source code if related

// paste test
Details
  • CodeceptJS version:
  • NodeJS Version:
  • Operating System:
  • puppeteer || webdriverio || testcafe version (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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codeceptjs/CodeceptJS

All issues in codeceptjs/CodeceptJS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.