Skip to content

Add Codecov upload to CI #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leynos merged 4 commits into from
Jul 5, 2025
Merged

Add Codecov upload to CI #182

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d9fdcfd
Add Codecov upload step
leynos Jul 5, 2025
70eb762
Add Codecov upload
leynos Jul 5, 2025
2880ec1
Update coverage documentation
leynos Jul 5, 2025
6f201fc
Fix list numbering
leynos Jul 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,4 +57,9 @@ jobs:
- name: Upload coverage data to CodeScene
if: env.CS_ACCESS_TOKEN
run: cs-coverage upload --format "lcov" --metric "line-coverage" "lcov.info"
- name: Upload coverage data to Codecov
# v5.4.3
uses: codecov/codecov-action@18283e04ce6e62d37312384ff67231eb8fd56d24
with:
files: lcov.info

7 changes: 6 additions & 1 deletion docs/multi-layered-testing-strategy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,11 @@ reviewers. This approach ensures that we establish a baseline of correctness
with simple tests before moving on to the more complex and subtle failure modes
that can emerge in an asynchronous, high-concurrency system.

Code coverage is measured with `cargo tarpaulin`. The CI workflow uploads the
generated `lcov.info` report to Codecov using a pinned version of the Codecov
GitHub Action (`18283e04ce6e62d37312384ff67231eb8fd56d24`, corresponding to
v5.4.3) to make coverage visible across pull requests.

## 2. Layer 1: Foundational Correctness (Unit & Integration)

**Objective:** To verify that each component behaves correctly in isolation and
Expand Down Expand Up @@ -473,7 +478,7 @@ workload.

2. **Latency:** The round-trip time for a single message.

3. **Push Latency:** The time from `push_handle.push()` to the client receiving
3. **Push latency:** The time from `push_handle.push()` to the client receiving
the frame.

**Measurable Objective:** For small frames on [localhost](http://localhost):
Expand Down