feat: Add scripts to analyze project test coverage

[denischilik]

Summary

• This PR contains two script files check_coverage.sh and check_coverage.py to build project coverage report
• To build report you can run check_coverage.sh from build folder.
• check_coverage.py contains COVERAGE_THRESHOLD which is used to highlight files with red if coverage less the threshold.
• Script doesn't display files which have 100% coverage

Testing Plan

• [*] Was this tested locally? If not, explain why.
• to check project test coverage you can run check_coverage.sh from build folder.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://mparticle-eng.atlassian.net/browse/SQDSDKS-7484

[nickolas-dimitrakas]

LGTM, discussed in-person with walkthrough and everything works as expected.

[BrandonStalnaker]

@jamesnrokt and @rmi22186 The implementation here is solid but if we'd prefer to use codeCov it doesn't make much sense to merge this. Should we schedule a meeting to decide this or have we already landed on one or the other?

More info from Denis on this where he compared the 2
https://docs.google.com/document/d/1mMxgIQwrE3vyQC6ZFGDi0F1BYd9BO9Jf_lk_0H-lKK4/edit?usp=sharing

[denischilik]

@jamesnrokt and @rmi22186 The implementation here is solid but if we'd prefer to use codeCov it doesn't make much sense to merge this. Should we schedule a meeting to decide this or have we already landed on one or the other?

Will you guys have chance to sync tomorrow?
I’ve sent an invite for a quick call.

[rmi22186]

My understanding is the current script in this PR is primarily for local development feedback to ensure PRs have a certain level of code coverage before pushing the branch up. Whereas codecov could be used to fail CI/CD if a certain level of code coverage is not attained. Is that accurate @denischilik

[denischilik]

That is true but not only for that, it will be also important during refactoring steps because we will need to understand if all implementation files have their related tests and to test that we maintain the same folder structure which we have for source files. Additionally it will be important to add test coverage limits for specific files.

…

On Thu, Aug 14, 2025 at 10:32 AM Robert Ing ***@***.***> wrote: *rmi22186* left a comment (mParticle/mparticle-apple-sdk#388) <#388 (comment)> My understanding is the current script in this PR is primarily for local development feedback to ensure PRs have a certain level of code coverage before pushing the branch up. Whereas codecov could be used to fail CI/CD if a certain level of code coverage is not attained. Is that accurate @denischilik <https://github.com/denischilik> — Reply to this email directly, view it on GitHub <#388 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BVUVHI7RODAZ2VV2APQJAS33NSMZJAVCNFSM6AAAAACDTPV5ZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOBYGY3TKNBXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Denis Chilik * [image: Rokt] <https://www.rokt.com> *M.* 2019529613 *A.* 175 Varick Street, Level 10, New York, NY 10014 <https://goo.gl/maps/EysMyzeDj6qyUQy49>

[mparticle-automation]

🎉 This PR is included in version 8.38.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀