Make errors with scenarios' name more clear #3655
Merged
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?
It slightly modifies the errors related with scenarios' name (like empty or prohibited characters).
Why?
Because, as stated in #3601, the current error messages are misleading.
I might be wrong, but in my opinion, I understand that every object under the
scenarios
key is a scenario definition, thus the key is the name of the scenario, not the name of the executor (type). Also, that's what can be guessed from our docs:So,
arbitrary_scenario_name
is the scenario name, andramping-vus
is the executor, it's name/type.Checklist
make lint
) and all checks pass.make tests
) and all tests pass.Related PR(s)/Issue(s)
Closes #3601