Better error message when no test system has been found #3185
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.
Impact
Description
As an occasionally forgetful developer, sometimes I neglect to specify which test systems I want to use or forget to update them when switching contexts. If I fail to specify any appropriate test system and run the command tests framework I will see a confusing error:
This change updates the error message to:
Things to be aware of
Throws an exception when there are no suitable test systems to run tests with. Previously spock would throw an exception when trying to build out the test case.
Things to worry about
This should not have any impact on the pipeline and should just be an enhancement for local development.