-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
By defining threshold for coverage I don't want to fail tests but to emit warning. #432
Comments
I've create a PR to address this, please see #433 |
Thanks for adding this. Did this make it into karma-coverage@2.0.3? I don't think it did. Can we have it in a new release of 2.0.4? |
bump |
@jginsburgn Can you help me release new version. I don't have permission to do it. |
@anthony-redFox @jginsburgn Any news on releasing a new version with this change? |
I have scheduled to work on this during this quarter. I will try to get to it as soon as possible. |
# [2.1.0](v2.0.3...v2.1.0) (2021-12-01) ### Bug Fixes * **deps:** update main and dev dependencies ([e7c020c](e7c020c)) ### Features * **reporter:** log coverage threshold as a warning fixed [karma-runner#432](https://github.com/jginsburgn/karma-coverage/issues/432) ([a6c95d8](a6c95d8))
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
In package
karma-coverage-istanbul-reporter
it was possible to add threshold for coverage and emit warning instead of failing tests. Here's config example:Since former package is now deprecated I tried migrating to
karma-coverage
.In package
karma-coverage
config is changed to:I can't add
emitWarning: true
to prevent tests from failing and emit simple warning.The text was updated successfully, but these errors were encountered: