Add code coverage reporting to CI (Codecov or Coveralls)

[davidmaronio]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Description

The contracts CI job installs cargo-tarpaulin and runs coverage but the XML report is never uploaded anywhere. Backend Jest and frontend tests also have no coverage tracking. Without a coverage badge and trend, it is impossible to see if contributions are adding or removing test coverage.

What Needs to Happen

• Upload cargo-tarpaulin XML to Codecov in the contracts job
• Add --coverage flag to backend Jest and upload the lcov report
• Add coverage thresholds: fail CI if coverage drops below 60%
• Add a coverage badge to README.md

Files

• .github/workflows/ci.yml
• README.md

Acceptance Criteria

• Coverage reports uploaded on every CI run
• Badge visible on README
• CI fails if coverage drops below threshold

[akinboyewaSamson]

@akinboyewaSamson has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

ℹ️ Repo Maintainers: To accept this application, review their application or assign @akinboyewaSamson to this issue.

[david87131]

@david87131 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi, Let me solve this issue and deliver a pr

ℹ️ Repo Maintainers: To accept this application, review their application or assign @david87131 to this issue.

[drips-wave]

Congratulations, @david87131! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @david87131: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @david87131 as part of the Stellar Wave Program's 4th Wave 🥳

😎 @david87131: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.