Repository navigation
Combined unit/integration test code coverage in CI - #289
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
stephen-derosa
left a comment
stephen-derosa
left a comment
There was a problem hiding this comment.
how does GTest know what % of integration is covered? For unit its a bit easier to understand "do all lines of code get hit" (give or take), but how does it work for integration?
Also looks like Devin left some reasonable comments
| run: | | ||
| set -euo pipefail | ||
| source scripts/set-test-tokens.sh | ||
| # TODO(BOT-477) Temporarily disable platform audio integration tests in CI until instability is resolved |
There was a problem hiding this comment.
should this be
# TODO(BOT-477) enable platform audio integration tests in CI when stable
?
There was a problem hiding this comment.
The comment is old, just showing up because of the changes, it meant disable platform audio tests via the GTest arg below until it works, which there is a fix in rust-sdks for (waiting on user-contributor to resolve devin flags)
@stephen-derosa It works the same both ways, integration test coverage is also lines of code/functions hit |
Co-authored-by: Cursor <cursoragent@cursor.com>
2 participants
Our prior code coverage numbers only included unit tests. This branch updates that to also include integration tests, which are also GTest-based. Just needed to wire up the coverage results better.