Add automation for code coverage in pushes

[maifeeulasad]

Description & Motivation

partial solution of #270

Related Issue(s)

#270

Testing

• Ran the script locally
• Couldnt run in my repo, due to some runner limitation I guess. It was stuck

Backwards-compatibility

Completly, as it is new feature

Is this a breaking change that will not be backwards-compatible? If yes, how so?
Non breaking change, as it is a new feature, working on a completely different branch

Documentation

Does the change require any updates to documentation? If so, where? Are they included?

Only one created script is documented inside, nothing more than that.

[mkorbel1]

This looks great! Do you want to try running this on your fork (update the runner so it uses the GitHub-hosted ones so it runs for you) to demo that it works?

[mkorbel1]

this runs coverage collection differently than the other script (https://github.com/intel/rohd/blob/main/tool/generate_coverage.sh), do you know if this approach is a newer/better way to collect coverage? should we update the other script? should these scripts be merged into one or one calls another instead of independent?

[maifeeulasad]

• I forgot to generate branch coverage, fixing that right away
• dart pub global run is deprecated, i think we should just use dart run, for our case dart test is just fine

I am willing to make modifications I just didn't know what that file was being used for that's why created this script completly bypassing that and generating svg along with it. Yeah, we can pass in some additional argument to tweak it's behavior. Wating to hear back from you!

ref: dart-lang/pub#3066

[mkorbel1]

would an error message be better there instead of just 0?

[maifeeulasad]

Care to suggest one please? I will update the PR accordingly

[mkorbel1]

question: why make our own SVG instead of using something like https://shields.io/ like we use for the README?

[maifeeulasad]

• it will push our github metrics up, ref: https://github.com/intel/rohd/graphs/traffic
• i like keeping 3rd party as much out as possible, that's why i kept it out. But I don't don't have anything against shields or badge io
• and if we use shields io, we need to keep push it to that branch, and write a railgruard to disable infinite action glitch

but if you want i can make adjustment for that

[maifeeulasad]

@mkorbel1 I pushed to a different branch for testing and yes it is working as it should

• this is the branch I tested with, https://github.com/maifeeulasad/rohd/tree/ci-repo-stat-maifee-test
• this is where the image got written, take a look at the filename please, it contains details regarding the branch name, https://github.com/maifeeulasad/rohd/blob/badges/coverage/ci-repo-stat-maifee-test.svg
• you can find more details on the action we ran: https://github.com/maifeeulasad/rohd/actions/runs/21357565364/job/61468509731

So basically the strategy is to generate report for each PR for main and push to that coverage branch. And the main readme file will point to that svg somewhere and we will get a beautiful badge there. This is the strategy for main branch.