Do you agree with this proposition :
- Add an Menu Option called "Run with timers disabled"
- This option will set a boolean on GuiPackage#getinstance() called
- Timers will consult this option to decide whether to run or not pause
- At end of run option will be reset (what would be the best way to
detect end, StandardJMeterEngine#run after waitThreadsStopped ?)
If you are Ok, I can implement it.
On Thu, Oct 13, 2011 at 1:09 PM, Philippe Mouawad <
> Hello Sebb,
> In my opinion this option would be useful only in Scripting Phase so
> through GUI.
> That's why I wanted it as a Menu Option or maybe "Run with timers disabled"
> My implementation idea was to test in parent delay() method a check for
> this option and return immediately if it is on.
> This would make it simple to implement and would not be persisted in Test
> Plan nor disabling of Timers would occur.
> What do you think ?
> On Thu, Oct 13, 2011 at 12:59 PM, <bugzi...@apache.org> wrote:
>> --- Comment #1 from Sebb <s...@apache.org> 2011-10-13 10:59:33 UTC ---
>> Rather than a Menu item, perhaps it should be a Test Plan option, which
>> mean checking for it in the engine code. But I think it would be simpler
>> If done via a Menu option, disabling is easy.
>> However, I assume there would be a re-enable option - what about timers
>> were originally disabled? Seems wrong to enable those, so the code would
>> to keep track of which Timers did not need re-enabling.
>> What if the Test Plan were updated in the mean-time? How could one keep
>> of which Timers to re-enable?
>> Using a Test Plan option would mean it would also work in non-GUI and
>> client-server mode.
>> Configure bugmail:
>> ------- You are receiving this mail because: -------
>> You reported the bug.
> Philippe Mouawad.