Add comprehensive code coverage infrastructure#436
Open
yashrajsapra wants to merge 4 commits intomainfrom
Open
Add comprehensive code coverage infrastructure#436yashrajsapra wants to merge 4 commits intomainfrom
yashrajsapra wants to merge 4 commits intomainfrom
Conversation
This commit adds complete code coverage support to ApraPipes with automatic CI/CD integration and local development tools. New Features: - CMake code coverage module with gcov/lcov integration - Automated coverage generation on every push/PR via GitHub Actions - Local coverage generation script for developers - Codecov.io integration for coverage tracking and trending - Coverage badges in README - Comprehensive documentation Files Added: - cmake/CodeCoverage.cmake: CMake module for coverage configuration - .github/workflows/code-coverage.yml: CI workflow for automated coverage - generate_coverage.sh: Local coverage generation script - codecov.yml: Codecov service configuration - docs/CODE_COVERAGE.md: Complete user documentation - COVERAGE_SETUP.md: Quick reference guide Files Modified: - base/CMakeLists.txt: Added CODE_COVERAGE option and coverage target - README.md: Added coverage section with badges and quick links Usage: Local: ./generate_coverage.sh CI: Automatic on push/PR Target: make coverage (in build directory) Configuration: - Coverage excludes: tests, third-party, system libraries - Target coverage: 70% line coverage - Reports: HTML + lcov format - Uploads to Codecov for tracking Benefits: - Visibility into test coverage - Automated coverage reporting - Easy local coverage generation - Coverage trends over time - PR coverage diffs To enable Codecov integration: 1. Visit https://codecov.io 2. Connect repository 3. Add CODECOV_TOKEN to GitHub secrets See docs/CODE_COVERAGE.md for complete documentation.
Contributor
Test Results Linux 1 files ±0 1 suites ±0 10m 16s ⏱️ -1s For more details on these failures, see this check. Results for commit f3ff6b2. ± Comparison against base commit 8933502. ♻️ This comment has been updated with latest results. |
- Update actions/upload-artifact from v3 to v4 - Pin CMake version to 3.29.6 for consistency - Fixes workflow failure due to deprecated artifact action
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit adds complete code coverage support to ApraPipes with automatic CI/CD integration and local development tools.
New Features:
Files Added:
Files Modified:
Usage:
Local: ./generate_coverage.sh CI: Automatic on push/PR Target: make coverage (in build directory)
Configuration:
Benefits:
To enable Codecov integration:
See docs/CODE_COVERAGE.md for complete documentation.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #[Issue]
Description
Precise description of the changes in this pull request
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Type Choose one: (Bug fix | Feature | Documentation | Testing | Other)
Screenshots (if applicable)
Checklist