This is one step closer to solving my problem.  However, I still have to somehow time 
things correctly. For example, if my test plan had the following
 
TestPlan
    ThreadGroup - 2 hour duration
        Once Only Controller
            HTTP Request - login
        Run Controller - 1 hour 57 minutes ?
            HTTP Request 1
            HTTP Request 2
        HTTP Request - logout

In Run Controller, I have to somehow make sure that I still have enough time to do the 
logout before the entire simulation ends (as set in ThreadGroup) but also just enough 
so that it doesn't do Run Controller again.  
 
I suppose I can do the following:
 
TestPlan
    ThreadGroup - loop once
        Once Only Controller
            HTTP Request - login
        Run Controller - 2 hours
            HTTP Request 1
            HTTP Request 2
        Once Only Controller
            HTTP Request - logout


But I would like the overall test plan to run 2 hours and not just the requests in Run 
Controller.  This is probably the closest solution for now that I can settle with.
 
Again, a Finally Controller is what I need. It would be nice to have option to 
complete a request and then jump to the Finaller Controller element when simulation is 
due.  Of course, to execute the Finally Controller, it would mean that the simulation 
time is actually longer than initially specified.  I will write up an enhancement 
request.  
 
If I were to start looking at how to implement a Finally Controller, where would be a 
good place to start? 
 
thanks,
mabel


Sebastian Bazley <[EMAIL PROTECTED]> wrote:Or a Runtime Controller, which I have just 
added to the 2.0 branch code.
This is like a loop controller, except that it runs for N seconds, instead
of N loops.

It should appear in the nightly builds
(http://gump.covalent.net/jars/latest/jakarta-jmeter-20/) in a day or so.
[The library zip can be picked up from
http://gump.covalent.net/jars/latest/jakarta-jmeter/ if you haven't already
got it - it rarely changes.]

Please remember that nightly builds are just that - they have not been
formally tested, and may not work at all.
If the build generally works, but the Runtime Controller has problems,
please log a bug.

S.
----- Original Message ----- 
From: "Remedy QA" 
To: "JMeter Users List" 
Sent: Wednesday, May 26, 2004 7:52 PM
Subject: RE: how to run a logout transaction once


> I'm sure that two thread groups can't access the same cookie and it would
be considered two different sessions, which would not work for me. But
thanks for the suggestions.
> What I need is a "finally" controller as Joe Casadonte mentioned, which
hasn't been implemented.
>
> "BAZLEY, Sebastian" wrote:
> In that case, you *might* be able to use two thread groups and run them
> consecutively.
>
> However, I don't think thread groups can access each others cookies or
> variables.
> This might cause you problems - cannot be sure from the information you
have
> provided.
>
> S.
> -----Original Message-----
> From: Remedy QA [mailto:[EMAIL PROTECTED]
> Sent: 26 May 2004 17:48
> To: JMeter Users List
> Subject: RE: how to run a logout transaction once
>
>
> The problem with this is that in Thread Group, it is scheduled to run for
2
> hours and loop forever. I am assuming that after 2 hours, the looping will
> stop.
>
> So, according to your suggestion, Simple Controller for login and logout
> will repeat and that is not what I want. I can use Once Only Controller
for
> login and the Loop Controller you suggested. However, the logout is the
> problem. I cannot use Once Only Controller for logout because the user
> should not logout until 2 hours has ended.
>
> thanks.
>
> "BAZLEY, Sebastian" wrote:
> Thread group
> Simple Controller
> Login
> Loop controller
> Random Controller
> Simple Controller
> Logout
>
> Or something similar.
> -----Original Message-----
> From: Remedy QA [mailto:[EMAIL PROTECTED]
> Sent: 25 May 2004 20:14
> To: JMeter User List
> Subject: how to run a logout transaction once
>
>
> I would like to have users run these in this order in a scheduled
simulation
> duration:
> 1. a first set of transactions once,
> 2. then run a second set randomly and repeatedly,
> 3. then finally when simulation time is near the end, run a thrid set of
> transactions once.
>
> For the first 2 sets, I realize I can use the Once Only Controller and
> Random Controller respectively. However, I don't know how to get the last
> set to run only once at the time I want.
>
> The last set of transactions is essentially logout. I would like the user
> to only login/logout once through the entire simulation. For the other
> transactions, I would like the users to repeat until the simulation time
has
> ended. The final action should be logout before the simulation ends.
>
> Can anyone think of a way to achieve this?
>
> Thanks,
> Mabel
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Friends. Fun. Try the all-new Yahoo! Messenger


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


                
---------------------------------
Do you Yahoo!?
Friends.  Fun. Try the all-new Yahoo! Messenger

Reply via email to