Coverage - Githubissues

Summary

Publish test coverage.

Details

Publish test coverage report in build summary (i.e. Show all checks -> Details -> summary). Removed the outdated badge from the Readme.

Motivation and Context

The badge in the Readme was outdated. The results in the summary was the easiest solution to show the coverage. There may be a better way I don't yet know of.

How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

[x] It is my own work, its copyright is implicitly assigned to the project and no substantial part of it has been copied from other sources (including Stack Overflow). In rare occasions this is acceptable, like in CMake modules where the original copyright information should be kept.
[x] I'm using the same code standards as the existing code (indentation, spacing, variable naming, ...).
[x] I've added tests for my code.
[x] I have verified whether my change requires changes to the documentation
[x] My change either requires no documentation change or I've updated the documentation accordingly.
[ ] My branch has been rebased to main, keeping only relevant commits.

cucumber / cucumber-cpp

Coverage #262