`run-multiple` command picks 0 feature files when `-c` CLI option is specified
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript, node.js
- Domain
- cli, testing-qa
Research direction
Start in lib/command/run-multiple.js around the custom configuration path handling, then trace how the resulting paths reach lib/codecept.js and globSync. Reproduce both run-multiple commands from the issue and verify that explicitly passing -c codecept.conf.js discovers and runs the configured feature files.
Written by the indexing model from the issue text.
Description
Let's assume we have codecept.conf.js config file in the project root with the following config:
exports.config = {
// other options go here
multiple: {
basic: {
browsers: ['chromium', 'firefox'],
},
},
gherkin: {
features: './features/*.feature',
steps: ['./step_definitions/steps.js'],
}
};
When running tests with:
codeceptjs run-multiple --all
all specified feature files are executed as expected.
However, when the -c CLI option is explicitly provided:
codeceptjs run-multiple --all -c codecept.conf.js
the command fails to identify and run the specified glob for the feature files, resulting in 0 features being picked.
Root cause:
The issue occurs due to the usage of path.resolve on paths when a custom configuration file is specified here. This results in invalid input for the globSync command, causing it to fail to resolve the glob patterns correctly 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 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 ·
-
stale
Difficulty 4/5 3-5 days Newbie friendliness 35/100
codeceptjs/CodeceptJS#5585 · 1 comment ·
All issues in codeceptjs/CodeceptJS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100