ci: Enable coverage and test results reporting#3618
Conversation
Enable coverage upload and test results reporting for sentry_link, sentry_supabase, and sentry_firebase_remote_config. These were commented out during initial publishing and never re-enabled. Also fixes incorrect directory paths in the coverage action inputs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## main #3618 +/- ##
===========================================
- Coverage 88.02% 57.79% -30.24%
===========================================
Files 304 16 -288
Lines 10372 417 -9955
===========================================
- Hits 9130 241 -8889
+ Misses 1242 176 -1066
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
sentry_link currently has ~4% test coverage (only 2 test files for 9 source files). Set min-coverage to 3% so CI passes while coverage reporting is enabled. This can be raised as test coverage improves. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The flutter-test action checks matrix.target (linux, macos, windows) to decide when to run tests and collect coverage. The supabase and firebase_remote_config workflows were using matrix.os instead, which meant tests were silently skipped and no coverage was generated. Switch to matrix.target to match isar.yml and other Flutter package workflows. Also remove unused web input from flutter-test step. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
| token: ${{ secrets.CODECOV_TOKEN }} | ||
| directory: packages/link | ||
| coverage: sentry_link | ||
| min-coverage: 3 |
There was a problem hiding this comment.
yes, the package really has that low coverage
There was a problem hiding this comment.
we adopted the package externally but we should in the future add some more coverage
There was a problem hiding this comment.
Pull request overview
Enables Codecov coverage uploads and JUnit test-results reporting for the sentry_supabase and sentry_firebase_remote_config packages, and re-enables coverage for sentry_link, aligning these workflows with the rest of the repo’s package CI reporting.
Changes:
- Re-enabled Codecov coverage uploads for
sentry_link,sentry_supabase, andsentry_firebase_remote_config. - Added Codecov test-results reporting steps for
sentry_supabaseandsentry_firebase_remote_config. - Standardized Flutter-package workflow matrices to use
matrix.target(macos/linux/windows) and fixed coverage actiondirectoryinputs topackages/....
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/supabase.yml | Switches to matrix.target and adds coverage + test-results uploads for the supabase package. |
| .github/workflows/link.yml | Re-enables coverage upload for sentry_link and corrects the coverage directory path. |
| .github/workflows/firebase_remote_config.yml | Switches to matrix.target and adds coverage + test-results uploads for firebase_remote_config. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Increased minimum coverage threshold from 55% to 85%.

📜 Description
Enable coverage upload and test results reporting for
sentry_link,sentry_supabase, andsentry_firebase_remote_config. These were commented out during initial publishing and never re-enabled.Also fixes incorrect
directorypaths in the coverage action inputs (e.g.link→packages/link,firebase_remote_config→packages/firebase_remote_config).💡 Motivation and Context
All other packages report coverage and test results to Codecov. These three were left behind with a TODO comment ("don't set coverage for now to finish publishing it"). The packages have been published for a while, so it's time to enable reporting.
Closes #3619
💚 How did you test it?
CI will validate — coverage and test-results steps will run on the next workflow execution for these packages.
📝 Checklist
sendDefaultPiiis enabled🔮 Next steps
Monitor CI to verify coverage uploads succeed and adjust
min-coveragethresholds if needed.#skip-changelog