You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jakarta.apache.org by bu...@apache.org on 2010/10/07 09:55:55 UTC

DO NOT REPLY [Bug 50053] New: Mark Ignored Timers in red

https://issues.apache.org/bugzilla/show_bug.cgi?id=50053

           Summary: Mark Ignored Timers in red
           Product: JMeter
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: Main
        AssignedTo: notifications@jakarta.apache.org
        ReportedBy: moreira@privasphere.com
                CC: hauser@acm.org


According to the documentation:
"Timers are only processed in conjunction with a sampler. A timer which is not
in the same scope as a sampler will not be processed at all. "

It would be very good to see timers that will be ignored marked in red or
yellow in the JMeter GUI.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org


DO NOT REPLY [Bug 50053] Mark Ignored Timers in red

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50053

--- Comment #2 from Luciana Moreira <mo...@privasphere.com> 2010-10-07 07:09:23 EDT ---
I agree with you in all points. But changing the indicators is what helps the
developer see where his/her errors might be. Given that "similar reasoning
applies to Assertions, Pre- and Post-Processors, and even Listeners", maybe we
can extend the idea to these elements.

For the design I would suggest to add a verification function in the method
that adds the element (or move it). This would reduce the runtime load to
verifications done on single elements, in contrast to the entire tree. I
haven't looked into the code to see what changes would be necessary though.

Of course, once the script is loaded, it would be necessary to do a full run.
If this turns out to be too heavy for certain scripts, we can always add a
property to disable it.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org


DO NOT REPLY [Bug 50053] Mark Ignored Timers in red

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50053

--- Comment #3 from Sebb <se...@apache.org> 2010-10-07 07:22:25 EDT ---
One could easily add a menu item to run the check manually, and not try to do
it automatically.

Note that adding or moving a sampler would potentially affect every other item
in the tree.

However, the main difficulty is likely to be implementing the check itself; the
test tree is one of the most complicated parts of JMeter.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org


DO NOT REPLY [Bug 50053] Mark Ignored Timers in red

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50053

--- Comment #1 from Sebb <se...@apache.org> 2010-10-07 06:20:57 EDT ---
Similar reasoning applies to Assertions, Pre- and Post-Processors, and even
Listeners.

I think this will be quite difficult to implement, and would need to be
carefully designed to ensure it did not impose a run-time load.

Also, unless all the samplers are added first, the indicators would keep
changing as a test plan was being updated.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org