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
Add code coverage support #35
Labels
enhancement
New feature or request
Comments
miroslavpojer
added a commit
that referenced
this issue
Nov 10, 2022
- added new plugin dependency - extended `readme.md` file with how to get code coverage report - extended build logic to add JaCoCo non-default settings
miroslavpojer
added a commit
that referenced
this issue
Nov 11, 2022
#35 - Add code coverage support - Added support for generation of code coverage report.
Release notes:
|
Reopen to fix existing solution. New version solve redundancy and format. |
miroslavpojer
added a commit
that referenced
this issue
Apr 20, 2023
- Added support for code coverage GitHub action check as part of PR. - Used Absa fork of JaCoCo solution - with scala method filtering.
miroslavpojer
added a commit
that referenced
this issue
Apr 21, 2023
- Added support for code coverage GitHub action check as part of PR. - Used Absa fork of JaCoCo solution - with scala method filtering.
Release notes:
|
miroslavpojer
added a commit
that referenced
this issue
Apr 27, 2023
- Removed Code coverage check for spark 3.
miroslavpojer
added a commit
that referenced
this issue
Apr 27, 2023
- Removed Code coverage check for spark 3.
miroslavpojer
added a commit
that referenced
this issue
May 5, 2023
Merged
miroslavpojer
added a commit
that referenced
this issue
May 5, 2023
- Update Jacoco version to get fix. - Bug: madrapps GH action uses not filtered summary information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Add code coverage support to be able measure code quality.
Feature
New ability to measure current code coverage as one of QA metrics.
Update:
The text was updated successfully, but these errors were encountered: