Hey hamepal,
    I had a vision of the IncludeController, ModuleController, and
TestFragments working like this when I contributed the TestFragment code.
Unfortunately, the IncludeController references aren't loaded until you run
the test plan which means that the ModuleController can't reference its
internals:-(

The best you have without a code change is one TestFragment per
IncludeController and then to use a TestFragment in your main Test Plan to
Include them all.  ModuleControllers can then reference each included file
to execute its contents.

I actually tried working on the flow you described because it would be
rather elegant and highly re-usable, but I ran into a ton of issues.

Hope this helps,

Anthony


On Sun, May 19, 2013 at 2:02 AM, [email protected] <[email protected]>wrote:

> I want to create a common test plan and define multiple test fragment in
> this
> file. I want to use some of the specific test fragment in the specific test
> plan. Here is outline of two different test plan.
>
>     common-test-plan.jmx
>      common-test-plan
>       |--TestFragment1
>       |   |-Sampler11
>       |
>       |--TestFragment2
>           |-Sampler21
>
>     Specific-test-plan.jmx
>      Some-Test-plan
>       |--ThreadGroup1
>          |-IncludeController
>          |-Module controller(accessing the Include controller)
>          |-Sampler1
>          |-Sampler2
>
>
>
> I used include controller to include the external test plan component. When
> I use the Module controller it just shows the include controller in the
> list. It doesn't show all test fragment present in the external test plan.
>
> Is there any way I can specifically use few of the test fragment present in
> the external test?
>
>
>
> --
> View this message in context:
> http://jmeter.512774.n5.nabble.com/How-to-access-different-test-fragment-present-in-external-test-plan-tp5716920.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to