You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2005/08/20 20:49:35 UTC

DO NOT REPLY [Bug 36285] New: - Need Sampler Group/include feature.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36285>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36285

           Summary: Need Sampler Group/include feature.
           Product: JMeter
           Version: unspecified
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: zaks@so.ct.edu


When attempting to write a modular test plan consisting of several logically
grouped samplers,files currently must be merged into an existing thread group as
a series of individual samplers.  This can lead to long, undifferentiated lists
of samplers in more complex test scenarios, and make maintenance of test groups
difficult.  My request is to have a level of grouping available between 'Thread
group' and 'Sampler' (say, 'Sampler Group').  You could merge a file into a
sampler group and manage your test scenarios better.  If you linked a sampler
group to a .jmx file, you would be able to move toward 'import'/#include type
functionality.

For example -- you have twenty scenarios that all use the same authentication
code that is saved as 'login.jmx'.  If the login protocol changes, currently you
would have to manually make changes to all twenty scenarios and merge them
directly into a Thread Group.

If you had a login sampler group (called 'Login') , you would be able to
visually identify all of the samplers associated with that functionality.  You
could make a change in login.jmx, delete the old samplers from Login, then merge
the new samplers into 'Login' from the file. 

Ideally, you should be able to link the sampler group to a file and have it
merge automatically when you open the test plan -- like a C #include or java
import. In the example above, the sampler group 'Login' could be directly linked
to the file login.jmx. This would make complicated test plans much easier to
maintain.

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

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