Fix test element name changing inside loop causing a bug#91
Open
alimans3 wants to merge 1 commit into
Open
Conversation
alimans3
force-pushed
the
fix-name-changing-in-loop-bug
branch
from
16745ac to
1d526ac
Compare
Author
Contributor
|
I don't work for Blazemeter anymore, sorry |
Author
|
@sebastianlorenzo88 @dnyaneshnagre |
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
2 participants
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.
Inside a loop, one can use multiple variables in the label that could cause the name to change in different iterations.
For example, you can use ${__jm__Loop__idx} to add the iteration number to the label.
In this case, the parallel sampler fails to run any iteration other than the first due to the thread naming,
A unit test was added that would fail without the change