I think its possible. But should you do that for functional tests? Nope.

I use the jmeter maven plugin to automate functional tests when they're
scripted with JMeter, in conjuction with the Jenkins' performance plugin.
In this case, tests are easily run, Everything in the forum is executed in
a single execution. Thus I keep one different script for each major test.
Its easier to update and if a script is re-usable then I use the Include
controller to re-use them. Its not the best and the cleanest method, but
the scripts are maintained in a way that they are readable and easy to
modify.

A similar method would be more advisable.

Adrian S


On Fri, Oct 4, 2013 at 1:07 PM, Jean FX <[email protected]> wrote:

> I meant
>
> The View Results Tree listener allows me to generate automated functional
> test results when each functional test is within a ThreadGroup result,
> because I am able to save the thread group's name in the results file.
>
>
>
> On Fri, Oct 4, 2013 at 11:56 AM, Jean FX <[email protected]> wrote:
>
> > Hello,
> >
> > Thanks for the reply.
> >
> > The View Results Tree listener allows me to generate automated functional
> > test results when each functional test is within a test result, because I
> > am able to save the thread name in the results file.
> >
> > I could not identify a result listener that saves the name of the
> > controller within which a sampler is located with the sampler results.
> >
> > Jean
> >
> >
> > On Fri, Oct 4, 2013 at 10:56 AM, bobMeliev <[email protected]> wrote:
> >
> >> Well, seems it will be hard for you to maintain and change Thread
> >> properties.
> >> If you want group functional tests why don't you use "Simple
> Controller"?
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://jmeter.512774.n5.nabble.com/Maximum-recommended-number-of-ThreadGroups-tp5718307p5718331.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