[CIVIS-9349] assign the single running test suite for a test if none found by test suite name #139
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?
Makes test suite assignment more robust by assigning the single runinng test suite to a test when no test suite found by name.
Motivation
There are cases where minitest test suite names fluctuate from test to test because of using external libraries like shoulda-context and/or activesupport concerns. While #134 fixed most of these cases there are still a very small chance of some test cases (inside anonymous classes?) that are skipped because of missing test suite id.
Thankfully, if minitest executes tests sequentially, there should be only one test suite running at a time: we can use it to assign "lost tests" to whichever test suite that is currently running.
How to test the change?
Unit tests are provided