add ci test coverage - #11
Conversation
|
The branch name violates the squad rules |
|
Also u can use codecov github action to display the code coverage report result @Radwa85 |
|
In general, you are good, but you need to change your commit to use Kover, not Jacoco |
|
mostafa-n3ma
left a comment
There was a problem hiding this comment.
nice work
consider reading my coments please
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
…overage # Conflicts: # app/build.gradle.kts # build.gradle.kts # gradle/libs.versions.toml
…overage # Conflicts: # build.gradle.kts # gradle/libs.versions.toml
1- Configured Kover to generate test coverage reports.
2- Created a GitHub Actions workflow that automatically runs tests and generates a coverage report on every pull request to the development branch.
3-Added logic to block PRs if overall coverage is below 80%