Skip to content

Conversation

@ammar-agent
Copy link
Collaborator

Problem

The integration-tests flag in codecov.yml was incorrectly configured to look for coverage in tests/** paths, but Jest collects coverage from src/** files (as specified in jest.config.js). This caused integration test coverage to not be properly tracked by Codecov.

Root Cause

  • Jest's collectCoverageFrom config specifies src/**
  • Integration tests in tests/** exercise application code in src/**
  • Test files (**/*.test.ts) are explicitly ignored in codecov config
  • The mismatch meant coverage data wasn't associated with the integration-tests flag

Solution

Updated the integration-tests flag to cover src/** paths, matching the actual coverage data generated by Jest.

Both unit tests and integration tests now correctly point to src/** since both generate coverage for source code, just through different test suites.

Testing

This PR will verify that integration test coverage is properly uploaded to Codecov when CI runs.

The integration-tests flag was incorrectly configured to look for coverage
in tests/** paths, but Jest collects coverage from src/** files (as
specified in jest.config.js). This caused integration test coverage to not
be properly tracked by Codecov.

Updated integration-tests flag to cover src/** paths, matching the actual
coverage data generated by Jest.
@ammario ammario marked this pull request as ready for review October 26, 2025 18:11
@ammario ammario added this pull request to the merge queue Oct 26, 2025
Merged via the queue into main with commit 9f2b981 Oct 26, 2025
13 checks passed
@ammario ammario deleted the ci-cov branch October 26, 2025 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants