Right now, the project's README file shows a hardcoded 100% coverage badge (see here). To provide more accurate and dynamic coverage data, it would be ideal to link the badge to a coverage reporting service.
Suggested Solution:
I recommend using a coverage service like Codecov which is easy to set up and widely supported. There are other alternatives such as:
Coveralls: A popular alternative for code coverage tracking.
SonarCloud: Provides code quality and security analysis alongside test coverage.
Code Climate: Another robust option for code quality metrics including coverage reporting.
See #1 for the Codecov integration example.
Goal: Replace the hardcoded 100% coverage badge with one that dynamically reflects the actual coverage results hosted by one of the services above.
Flexonze
commented
1 month ago
Right now, the project's README file shows a hardcoded 100% coverage badge (see here). To provide more accurate and dynamic coverage data, it would be ideal to link the badge to a coverage reporting service.
Suggested Solution:
I recommend using a coverage service like Codecov which is easy to set up and widely supported. There are other alternatives such as:
See #1 for the Codecov integration example.
Goal: Replace the hardcoded 100% coverage badge with one that dynamically reflects the actual coverage results hosted by one of the services above.