The test fragment must be inside the included file, for the include
controller will ignore any test element not placed under a test fragment.
You can however have a test fragment as parent of the include controller,
which includes a file containing another test fragment. I use this setup
for example to be able to point to the include controller from a module
controller in the thread group.
To summarize this is the way to do it:
Included file:
Test Plan
|--Test fragment
|-- sampler 1
|-- sampler 2
Test project:
Test Plan
|--Test fragment
| |-- Include controller (pointing to included file above)
|-- Thread group
|-- Sampler 3
|-- Module controller (pointing to Test Fragment > Include
controller)
|-- Sampler 4
This will be run as:
Sampler 3
sampler 1
sampler 2
Sampler 4
On 22 October 2013 14:49, Robin D. Wilson <rwils...@gmail.com> wrote:
> So let me understand, do I need to put the "Test Fragment" inside the
> included file, or do I put the Include Controller inside a Test Fragment?
>
> --
> Robin D. Wilson
> VOICE: 512-777-1861
>
>
>
> On Oct 22, 2013, at 6:52 AM, Nicola Ambrosetti Brolin <
> ambrosetti.nic...@gmail.com> wrote:
>
> I might add (since I was the reporter of bug 55464) that it is confusing
> that when using "Save selection as" the produced jmx project has the
> selected steps sitting right under the test plan, instead of being under a
> test fragment. Thus one could be led to believe that the saved selection
> could be included as is. However this is not the case: the include
> controller will completely ignore anything in the included project that is
> not child of a test fragment.
>
> Cheers,
>
> Nicola
>
>
> On 22 October 2013 10:58, UBIK LOAD PACK Support
> <supp...@ubikloadpack.com>wrote:
>
> > Hello,
> > I think you are misusing Test Fragments.
> >
> > Test Fragment should be in INCLUDED Test Plan not INCLUDER.
> >
> > So in your case they should be Login.jmx and Timer.jmx.
> > While according to what you show and to log file they are in INCLUDED
> Test
> > Plan.
> >
> > I think this is what changes mentions:
> >
> > - The correct way to include Test Elements is to use *Test Fragment *as
> > stated in documentation of *Include Controller *.
> > - The include controller is designed to use an external jmx file. To
> use
> > it, create a Test Fragment underneath the Test Plan and add any desired
> > samplers, controllers etc. below it. Then save the Test Plan. => The
> > file
> > is now ready to be included as part of other Test Plans.<=
> >
> >
> > Regards
> >
> >
> > On Tue, Oct 22, 2013 at 4:13 AM, Robin D. Wilson <rwils...@gmail.com>
> > wrote:
> >
> >> That is exactly what I'm using (Test Fragments)...
> >>
> >> --
> >> Robin D. Wilson
> >> VOICE: 512-777-1861
> >>
> >>
> >>
> >> On Oct 21, 2013, at 6:49 PM, UBIK LOAD PACK Support <
> >> supp...@ubikloadpack.com> wrote:
> >>
> >> Hello,
> >> Incompatible changes explains your issue:
> >>
> >> - jmeter.apache.org/changes.html
> >>
> >> - In previous versions, *IncludeController *could run Test Elements
> >> located inside a *Thread Group *, this behaviour ( *which was not
> >> documented *) ould result in weird behaviour, it has been removed in
> >> this version (see Bug
> >> 55464<https://issues.apache.org/bugzilla/show_bug.cgi?id=55464> ).
> >> The correct way to include Test Elements is to use *Test Fragment *as
> >> stated in documentation of *Include Controller *.
> >>
> >>
> >> Regards
> >> @ubikloadpack
> >>
> >>> On Tuesday, October 22, 2013, Robin D. Wilson wrote:
> >>>
> >>> I have a test that includes some test fragments using an 'Include
> >>> Controller', and then those test frags are used throughout the
> >>> thread groups by being added in a 'Module Controller'. When I load my
> >>> test, I get these messages in the log:
> >>>
> >>> ---------------------------------------
> >>>
> >>> 2013/10/21 18:20:33 INFO - jmeter.gui.action.Load: Loading file:
> >>> X:\Tests\JMeter\WizardHome\TestSuites\Stress Test\W101 Login
> >>> Stress Generator_wTestFrag.jmx
> >>> 2013/10/21 18:20:33 INFO - jmeter.services.FileServer: Set new
> >>> base='X:\Tests\JMeter\WizardHome\TestSuites\Stress Test'
> >>> 2013/10/21 18:20:34 INFO - jmeter.services.FileServer: Set new
> >>> base='X:\Tests\JMeter\WizardHome\TestSuites\Stress Test'
> >>> 2013/10/21 18:20:34 INFO - jmeter.control.IncludeController:
> >>> loadIncludedElements -- try to load included module:
> >>> X:\Tests\JMeter\WizardHome\TestSuites\Functional Units\Login.jmx
> >>> 2013/10/21 18:20:34 WARN - jmeter.control.IncludeController: No Test
> >>> Fragment was found in included Test Plan, returning empty
> >>> HashTree
> >>> 2013/10/21 18:20:34 INFO - jmeter.control.IncludeController:
> >>> loadIncludedElements -- try to load included module:
> >>> X:\Tests\JMeter\WizardHome\TestSuites\Functional
> > Units\Utility\Timer.jmx
> >>> 2013/10/21 18:20:34 WARN - jmeter.control.IncludeController: No Test
> >>> Fragment was found in included Test Plan, returning empty
> >>> HashTree
> >>> 2013/10/21 18:20:34 INFO - jmeter.control.IncludeController:
> >>> loadIncludedElements -- try to load included module:
> >>> X:\Tests\JMeter\WizardHome\TestSuites\Functional Units\Login.jmx
> >>> 2013/10/21 18:20:34 WARN - jmeter.control.IncludeController: No Test
> >>> Fragment was found in included Test Plan, returning empty
> >>> HashTree
> >>> 2013/10/21 18:20:34 INFO - jmeter.control.IncludeController:
> >>> loadIncludedElements -- try to load included module:
> >>> X:\Tests\JMeter\WizardHome\TestSuites\Functional
> > Units\Utility\Timer.jmx
> >>> 2013/10/21 18:20:34 WARN - jmeter.control.IncludeController: No Test
> >>> Fragment was found in included Test Plan, returning empty
> >>> HashTree
> >>>
> >>>
> >>> --------------------------------------
> >>>
> >>> NOTE: The repeat of the INFO+WARN messages about trying to load the
> >>> IncludeController is puzzling, since there are only 2 Include
> >>> Controllers in the test plan... Not sure why it appears to be trying to
> >>> load each of them twice.
> >>>
> >>> This same test works perfectly on JMeter 2.9 (and earlier).
> >>>
> >>> FYI, the test looks like this:
> >>>
> >>> Test Plan
> >>> Setup stuff (User Defined Vars, Requests Defaults,
> > Cookie
> >>> Manager, etc.)
> >>>
> >>> "Includes" Test Fragment
> >>> Include Controller - Login.jmx
> >>> Include Controller - Timer.jmx
> >>>
> >>> "Timer Start" Thread Group
> >>> User Parameters - "Timer Start"
> >>> Module Controller - "Timer" (from
> > "Includes/Timer"
> >>> module above)
> >>>
> >>> "Login" Thread Group
> >>> User Parameters - "Login"
> >>> Module Controller - "Login" (from
> > "Includes/Login"
> >>> module above)
> >>>
> >>> "Timer End" Thread Group
> >>> User Parameters - "Timer End"
> >>> Module Controller - "Timer" (from
> > "Includes/Timer"
> >>> module above)
> >>> Tree Listener (only shows 'errors')
> >>> Summary Report Listener
> >>>
> >>> Near as I can tell, each thread group runs - for as many threads as I
> >>> expect - but nothing happens within the thread group (e.g.,
> >>> none of the 'Module Controllers' actually do anything).
> >>>
> >>> BTW, if I "merge" the two "Included" test fragments - into the
> > "Includes"
> >>> Test Fragment - and re-configure my module controllers to
> >>> point to the merged stuff, it works. So it appears to be a problem with
> >>> the Include Controller not actually loading my stuff.
> >>>
> >>> I have noted a significant performance boost on this new version of
> >>> JMeter, but I can't use it if I can't get the Include Controller
> >>> to work... So any help would be very appreciated.
> >>>
> >>> --
> >>> Robin D. Wilson
> >>> Sr. Director of Web Development
> >>> KingsIsle Entertainment, Inc.
> >>> VOICE: 512-777-1861
> >>> http://www.kingsisle.com
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> > <javascript:;>
> >>> For additional commands, e-mail: user-h...@jmeter.apache.org
> >> <javascript:;>
> >>>
> >>>
> >>
> >> --
> >>
> >> Regards
> >> Ubik Load Pack <http://ubikloadpack.com> Team
> >> Follow us on Twitter <http://twitter.com/ubikloadpack>
> >>
> >>
> >> Cordialement
> >> L'équipe Ubik Load Pack <http://ubikloadpack.com>
> >> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> >> For additional commands, e-mail: user-h...@jmeter.apache.org
> >>
> >>
> >
> >
> > --
> >
> > Regards
> > Ubik Load Pack <http://ubikloadpack.com> Team
> > Follow us on Twitter <http://twitter.com/ubikloadpack>
> >
> >
> > Cordialement
> > L'équipe Ubik Load Pack <http://ubikloadpack.com>
> > Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
