feat(ci): Last CI step checking for non-exercised tests#4533
Open
pfcoperez wants to merge 4 commits into
Open
Conversation
…de are exercised on each combination
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Member
Author
QA Validation
|
Contributor
❌ Test FailureAnalysis: Not flaky — the tests passed, but a deterministic CI meta-check failed identically across all matrix jobs because the newly added test TestApiMongo is never exercised in CI, indicating a missing CI wiring/config for that test. |
This reverts commit f5edf6c.
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
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.


These changes add a last step in the build that compares the list of executed top level test functions with the list of existing top-level test functions in the source branch code.
📝 Doesn't detect missing runs of run-time generated tests like table based test cases.
📝 Only relevant for test cases defined under
./flow