feat: add code coverage report in ci #422
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. enable test phase by default via set maven.test.skip=false 2. add code coverage report in test phase by jacoco
1. add code coverage report in test phase by jacoco
2 tasks
…rage_report_via_jacoco # Conflicts: # pom.xml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of the pull request
before change:
No coverage report in build result
post change:
since
mvn clean test, the report will be generated as aggregated version in test modulefastexcel-test/target/site/jacoco-aggregate/index.html
BTW, there is a gap as current project test scope only covered test package as cn/idev/excel/test/core
As previous discussion in PR #390 & #392 , the project won't trigger all test case in CI with package demo,temp,util , so the actual coverage might be greater than above ratio of screenshot.
The coverage ratio looks good within IDE as below
What's changed?
pom.xml
fastexcel-test/pom.xml
Checklist