You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Serguei Belikov <sb...@tucows.com> on 2005/09/17 00:15:03 UTC
How it can be implemented?
Hi,
I have a requirement for test plans to share some common elements and
tree branches. For instance, the idea is to have a lot of test plans
that refers to the same login procedure (set of HTTP samplers,
assertions, extractors, configuration, and so on). If login procedure is
changed, than after modifying it in one file all test plans will use
this updated procedure. Otherwise, in our company it will be required to
manually update ~300 files, which is very efforts consuming. Any
suggestions about how it can be implemented effectively?
--
Regards,
Serguei Belikov
Sr. Developer
Tucows Inc.
sbelikov@tucows.com
(416) 535-0123 Ext. 1297
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: How it can be implemented?
Posted by Peter Lin <wo...@gmail.com>.
there's a new include controller which should be out with 2.1.1.
it will allow you to make a series of requests in the workspace and then
save it as a module. the module can then be used in the include controller.
peter
On 9/16/05, Manish Mathuria <mm...@yahoo.com> wrote:
>
> I am going through the same issue. For now I am creating "modules" which
> are equal to functional parts of the SUT (such as login) and putting them
> all in, workbench. I save this workbench as a separata file. So this will
> eventually become a library for me/others who want to use this functional
> modules.
>
> When I create a new test plan I merge this workbench file to my test plan
> jmx file. I only put module controllers that call these modules in the
> workbench in my test plan (ofcourse I have listeners, configurations and
> such in my test plan).
>
> Please let me know if some one else uses a better way to segment test
> cases.
> Manish
>
> PS. Documentation states, that you would not be able to use master-slave
> multi machine configuration when you use module controller (I have no idea
> why!). I am planning to manully merge result files anyway. Again if there is
> a way to achieve the modularity with out sacrificing multi machine
> operations please let me know...
>
>
>
> Serguei Belikov <sb...@tucows.com> wrote:
> Hi,
>
> I have a requirement for test plans to share some common elements and
> tree branches. For instance, the idea is to have a lot of test plans
> that refers to the same login procedure (set of HTTP samplers,
> assertions, extractors, configuration, and so on). If login procedure is
> changed, than after modifying it in one file all test plans will use
> this updated procedure. Otherwise, in our company it will be required to
> manually update ~300 files, which is very efforts consuming. Any
> suggestions about how it can be implemented effectively?
>
> --
> Regards,
> Serguei Belikov
> Sr. Developer
> Tucows Inc.
> sbelikov@tucows.com
> (416) 535-0123 Ext. 1297
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
Re: How it can be implemented?
Posted by Manish Mathuria <mm...@yahoo.com>.
I am going through the same issue. For now I am creating "modules" which are equal to functional parts of the SUT (such as login) and putting them all in, workbench. I save this workbench as a separata file. So this will eventually become a library for me/others who want to use this functional modules.
When I create a new test plan I merge this workbench file to my test plan jmx file. I only put module controllers that call these modules in the workbench in my test plan (ofcourse I have listeners, configurations and such in my test plan).
Please let me know if some one else uses a better way to segment test cases.
Manish
PS. Documentation states, that you would not be able to use master-slave multi machine configuration when you use module controller (I have no idea why!). I am planning to manully merge result files anyway. Again if there is a way to achieve the modularity with out sacrificing multi machine operations please let me know...
Serguei Belikov <sb...@tucows.com> wrote:
Hi,
I have a requirement for test plans to share some common elements and
tree branches. For instance, the idea is to have a lot of test plans
that refers to the same login procedure (set of HTTP samplers,
assertions, extractors, configuration, and so on). If login procedure is
changed, than after modifying it in one file all test plans will use
this updated procedure. Otherwise, in our company it will be required to
manually update ~300 files, which is very efforts consuming. Any
suggestions about how it can be implemented effectively?
--
Regards,
Serguei Belikov
Sr. Developer
Tucows Inc.
sbelikov@tucows.com
(416) 535-0123 Ext. 1297
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com