We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In many cases, test elements need "per-thread-group-scope" variable or "per-test-execution-scope" variable. For instance:
static final Map<ThreadGroup, timerState>
The current approach of element implements TestStateListener causes issues like #6174, #6165
element implements TestStateListener
We might need something like https://docs.gradle.org/current/userguide/build_services.html or https://github.com/google/guice/wiki/Scopes so the plugin authors can explicitly declare "per-test-execution state objects", so they do not need to implement TestStateListener in the test elements.
TestStateListener
It might be worth deprecatign TestElement implements TestStateListener at least to discourage that usage pattern.
TestElement implements TestStateListener
No response
5.6.2
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Use case
In many cases, test elements need "per-thread-group-scope" variable or "per-test-execution-scope" variable.
For instance:
static final Map<ThreadGroup, timerState>
The current approach of
element implements TestStateListener
causes issues like #6174, #6165Possible solution
We might need something like https://docs.gradle.org/current/userguide/build_services.html or https://github.com/google/guice/wiki/Scopes so the plugin authors can explicitly declare "per-test-execution state objects", so they do not need to implement
TestStateListener
in the test elements.It might be worth deprecatign
TestElement implements TestStateListener
at least to discourage that usage pattern.Possible workarounds
No response
JMeter Version
5.6.2
Java Version
No response
OS Version
No response
The text was updated successfully, but these errors were encountered: