Create a GitHub CI workflow for publishing unit test reports

[rdmark]

Build and run unit tests with code coverage support, execute tests to get a junit report, publish the report, generate and publish a lcon style code coverage report

[rdmark]

@msteinert I now have unit test result reports and code coverage reports up and running here in GitHub CI! See f.e. https://github.com/msteinert/bstring/actions/runs/16941054221

These actions that I'm using have the ability to decorate PRs with the reports for an even nicer integration. Would you be open to granting the two permissions required? (create an issue comment and create a check run)

[msteinert]

To enable this I need to add a GitHub seccret GITHUB_TOKEN with the two permissions you mentioned?

[rdmark]

Hmm, actually let me try first if it's a simple missing permissions in the workflow definition.

[github-actions]

LCOV of commit 42caa13 during Unit Tests #7

Summary coverage rate:
  lines......: 86.1% (4284 of 4974 lines)
  functions..: 96.5% (248 of 257 functions)
  branches...: 60.9% (2711 of 4448 branches)

Files changed coverage rate: n/a

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rdmark]

@msteinert Problem solved. No need to prepare any token. The coverage report is now posted to the PR!

Now the only outstanding issue is that the code coverage stats includes the test code itself, which inflates the coverage stats. There's a known limitation with the interaction between meson and lcov as described in the issue below.

mesonbuild/meson#3287

I can attempt a workaround.

[msteinert]

Nicely done! It would be really cool if the gcovr report could available.

Maybe this (publish to Coveralls)? https://github.com/marketplace/actions/gcovr-action

Or is it overkill for this project?