-
### Ticket Contents
### Description
To enhance the code quality monitoring for the AMRIT API repositories, we need to integrate JaCoCo test coverage reports with SonarCloud. This integration wil…
-
-
# Overview
For now it doesn't work well.
# Tasks
- [ ] remove test itself coverage from frontend
- [ ] send to coveralls/codecov both backend/frontend coverage if repo will not be split
-…
-
My workspace has about 30 packages and I am trying to report coverage per-package in the workspace but right now if I run tarpaulin on a single package, either via `cargo tarpaulin -p package1` or by …
-
**Describe the bug**
When `use_coverage` is enabled, Go packages that have `_test` packaged test files (ie. for the package `foo`, the tests are in the same folder but are in the `foo_test` package a…
-
Since switched to [jest-light-runner](https://www.npmjs.com/package/jest-light-runner) (#470), code coverage reporting is no longer working.
[jest-light-runner](https://www.npmjs.com/package/jest-l…
-
cc @magnatelee @marcinz @manopapad @m3vaz
There is an interest in providing code coverage reporting, and enforcing minimum code coverage levels. This can be a somewhat involved topic even for sma…
-
See #79 for Codacy addition. I have already registered this repo with Codacy. The only thing we need is the coverage reporting (via Istanbul) shown here:
https://github.com/codacy/node-codacy-cover…
-
Let's hook up https://github.com/rpl/flow-coverage-report/ to web-ext! Ideally we'd want to pick a target for coverage (100%? 95%? something) and make the tests fail if it dips below that percentage.
-
Business Reason
As a user, I will see blank dates in the coverage dates for Form 3x when I select a ‘non-standard’ (outside of the standard monthly and quarterly) report type.
Acceptance criteria
*…