karma-runner / karma-runner/karma
v6 CLI arg verification breaks extra args parsing
- Dominant language
- JavaScript
- Stars
- 12k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hello, currently karma CLI doesn't allow explicit test files as arg so we're passing them at the end and parse them out in `karma.conf.js` and v6 breaks it so I'm essentially asking if:
1. Karma CLI can support explicit test files passed in as args OR
2. Make strict mode be optional
I understand that this is not previously a feature but a lot of stack overflow answers seem to point to this mechanism being the workaround to further modify karma conf using CLI arg.
The way we're calling it is essentially `karma start karma.conf.js [testFiles...]`
Thanks!
Contributor guide
Research direction
Start by tracing v6 CLI argument verification for the `karma start karma.conf.js [testFiles...]` invocation and how trailing arguments are handled before they reach `karma.conf.js`. Determine whether explicit test files or optional strict mode is the intended behavior; done means the chosen behavior works without breaking CLI argument handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100