You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Anthony Johnson <an...@gmail.com> on 2010/12/27 17:49:33 UTC
Why are IncludeController loaded at startup and at Test Start?
Hello list,
I'm in the implementation stage of another enhancement for the
IncludeController and needed some feedback from Devs who know the code
a little better than myself.
My Enhancement: I want to be able to see the included trees that are
being executed including listeners so that the test can more easily be
debugged, monitored and modular. I know this can be accomplished, but
the results have been under-whelming which is the trigger for this
e-mail.
My Questions:
1. Why are IncludeControllers loaded on Test Plan load and also on
Test Run start? Couldn't we just load it once when we are compiling
the test at Test runtime?
2. If we loaded at Test runtime only couldn't we then use standard
variables for finding the include files instead of the
includecontroller.prefix property?
3. Are than any objections to modifying the GUI JTree to display the
Included Elements as part of that tree. My "current" vision is that a
"Clear/Clear All" would purge the JTree of ReplaceableController trees
and would cause them to be re-loaded at the next Test Run. A
reloading of Included files would be accomplished by simply doing a
"Clear All"
Thoughts?
Thanks,
Anthony
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Why are IncludeController loaded at startup and at Test Start?
Posted by sebb <se...@gmail.com>.
On 27 December 2010 16:49, Anthony Johnson <an...@gmail.com> wrote:
> Hello list,
> I'm in the implementation stage of another enhancement for the
> IncludeController and needed some feedback from Devs who know the code
> a little better than myself.
>
> My Enhancement: I want to be able to see the included trees that are
> being executed including listeners so that the test can more easily be
> debugged, monitored and modular. I know this can be accomplished, but
> the results have been under-whelming which is the trigger for this
> e-mail.
>
> My Questions:
>
> 1. Why are IncludeControllers loaded on Test Plan load and also on
> Test Run start? Couldn't we just load it once when we are compiling
> the test at Test runtime?
Sorry, no idea without delving deep into the code.
> 2. If we loaded at Test runtime only couldn't we then use standard
> variables for finding the include files instead of the
> includecontroller.prefix property?
Probably.
> 3. Are than any objections to modifying the GUI JTree to display the
> Included Elements as part of that tree. My "current" vision is that a
> "Clear/Clear All" would purge the JTree of ReplaceableController trees
> and would cause them to be re-loaded at the next Test Run. A
> reloading of Included files would be accomplished by simply doing a
> "Clear All"
No objections, so long as this does not cause problems for non-GUI and
server modes.
Also, I think this should be optional, as updating the tree will cause
additional overhead, and the trade-off may not suit everyone.
> Thoughts?
>
> Thanks,
>
> Anthony
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org