karma-runner / karma-runner/karma
Exit with a special code for tool/browser failure
- Dominant language
- JavaScript
- Stars
- 12k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
### Expected behavior
If karma tests fail due to browser issue karma single run should exit with an exit code to differentiate between a 'tool failure' vs. a 'test failure'.
Would like karma to 'exit(100)' to indicate this type of failure or the error code must be configurable for these situations.
### Actual behavior
Karma always exits with a '1' status whenever anythinng goes wrong, test failure or browser failure
### Enviroment Details
- Karma version (output of `karma --version`):
- Relevant part of your `karma.config.js` file
Contributor guide
Research direction
Start by tracing Karma's single-run exit handling and how browser failures are distinguished from test failures. Determine where the current status 1 is produced and define how a separate or configurable tool-failure code should behave; done means single runs reliably return distinguishable statuses without changing test-failure behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100