Support ${...} for TestElement.enabled property
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
### Use case
It might be helpful to disable some of the bits in the test plan when launching the script from the commandline.
For instance:
* Exclude some of the thread groups
* Exclude some of the listeners (e.g. saving the responses)
### Possible solution
Move `enabled` checkbox to the common UI side by side with `name`, `comments`.
### Possible workarounds
_No response_
### JMeter Version
5.5
### Java Version
_No response_
### OS Version
_No response_
Contributor guide
Research direction
Start by tracing the TestElement.enabled property and the common UI fields named in the proposal, then inspect the command-line launch path for property expansion. Done means a command-line ${...} value can control enabled test-plan elements, with the proposed UI placement resolved consistently for thread groups and listeners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100