use framework name as test module name to make test fingerprints stable #131
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.
What does this PR do?
Fixes customer-reported issue with flaky test detection after test suite level visibility release.
Bug description
Currently
test_module_end
events have the same name astest_session_end
which could be different between test runs: we use test command value this and test command could include variable data (like --seed param). The problem is that test module name is part of test fingerprint, and unstable fingerprints make flaky test detection impossible.How is it fixed?
We change test module name to be just the test framework name (minitest, rspec, or cucumber). NOTE: This change will cause fingerprint updates for all current tests.