Hi,

As far as I understand, JMeter UI lacks feedback for "error prone"
configurations. It would be so much better if JMeter would have "spell
checker" integrated, so it warned on "bad test plan patterns".

Was there a discussion/plan to implement that?
I'm sure lack of that checker makes it very hard to integrate new features
since almost every new feature can be misused, so "decline a feature" is
basically the only way to protect user from misuse.

For instance,
1) A proper way to place inter-page timers is to wrap the timer into some
kind of "test action". So, if user has "page, timer, page, timer" kind of
test plan, that deserves a warning "you might probably want to wrap
timers..."
2) If user places constant throughput timer at the very top of the test
plan, that is probably wrong. CTT should likely to be wrapped into some
sampler.
3) If user references non-existing variable, then you don't know that until
you start the test. For instance, JMeter know which variable is produced by
regexp extractor, so it can check if user uses that or not.
For instance, there might be a warning like "unused regexp extractor", etc.
4) "Adjust timers" feature. Even though it might be useful, it might easily
be misused. I think having some warnings would improve UX for this
particular feature as well.

Vladimir

Reply via email to