Skip to content

docs: Document command to generate local html coverage report#1832

Open
tpoliaw wants to merge 1 commit intomainfrom
cov-docs
Open

docs: Document command to generate local html coverage report#1832
tpoliaw wants to merge 1 commit intomainfrom
cov-docs

Conversation

@tpoliaw
Copy link
Contributor

@tpoliaw tpoliaw commented Jan 20, 2026

No description provided.

@tpoliaw tpoliaw requested a review from a team as a code owner January 20, 2026 15:36
@codecov
Copy link

codecov bot commented Jan 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.04%. Comparing base (07c462c) to head (410c3ec).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1832   +/-   ##
=======================================
  Coverage   99.04%   99.04%           
=======================================
  Files         306      306           
  Lines       11589    11589           
=======================================
  Hits        11478    11478           
  Misses        111      111           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tpoliaw tpoliaw added documentation Improvements or additions to documentation Docsathon Tickets that may be tackled during the Docsathon, 27-8th August 2025 labels Jan 21, 2026
Copy link
Contributor

@Villtord Villtord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not critically related to this change - do we have control over order of How-to pages? It feels like "checking coverage" should be close to "running tests" for me?

@tpoliaw
Copy link
Contributor Author

tpoliaw commented Jan 26, 2026

It looks like it's alphabetical order with H1 sections promoted to full pages below their parent page (eg `Reusing an existing class follows Creating a new device because they're the same source file.

This is probably worthy of its own issue. The two example above probably shouldn't be listed as separate how-to guides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Docsathon Tickets that may be tackled during the Docsathon, 27-8th August 2025 documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments