Well, there are many ways to do it, and I did not know your specific requirements, so I just listed them all. Throughput can help direct different threads to different parts of the tree, though it doesn't guarantee what you seem to need.
What you need is actually very simple, if I understand. Logging in each thread as a different user involves using the __CSVRead function and populating the file with pairs of user/password. You would probably want to use them in the User Parameters component. I don't know if you're familiar with these JMeter elements. If not, I'd be happy to send you a little sample test script that shows their use. -Mike On Tue, 2004-12-14 at 19:57, Mark Zellers wrote: > As you said, the devil is in the details of ThreadGroup 2. It would > seem more straightforward if there were a container that expressed > "execute these things serially" vs. "execute these things in parallel", > rather than having that be a property of the test plan. Then I could > easily take the existing parallel thread groups (one per user) and nest > them inside a parallel container. > > I don't see how the Throughput controller or the Random controller can > guarantee that only one user ID will be used at a time, which is a > requirement for my application (logging in a second time logs out the > previous session with the same user id). > > Mark Z. > > -----Original Message----- > From: Michael Stover [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 14, 2004 4:50 PM > To: JMeter Users List > Subject: Re: Initialization/Run Users/Cleanup > > Well, essentially, you have the solution, except that JMeter supports > all that in one single script. > > You can add more than one ThreadGroup to JMeter. Normally, JMeter will > execute these ThreadGroups in parallel, but the Test Plan element has an > option that lets you tell JMeter to run them serially. > > So, your test would have 3 ThreadGroups: > ThreadGroup 1: 1 simulated user, admin goes in and does startup stuff. > ThreadGroup 2: many simulated users do their thing > ThreadGroup 3: 1 simulated user, admin goes in and does finishing stuff. > > The difficulty will be in threadgroup 2 where you say you want different > users performing different actions. However, there are many ways to have > different threads perform very different test scripts in JMeter, either > through use of the Access Log Sampler, Throughput Controller, Random > Controller, If controller (you can even write a top level if controller > that sends each thread through a different set of tests, if you like). > The possibilities are quite literally endless. And complicated :-) > > -Mike > > On Tue, 2004-12-14 at 19:28, Mark Zellers wrote: > > I want to add some initialization/cleanup steps to my test such that > it > > can be run repeatedly. > > > > > > > > To do this, I want to be able to have a single user login, perform a > > simple administrative action and log out. Then I want to run some > > number of users, each performing a different script all running at > once > > for a period of time. When those have completed, I want the > > administrator to log in again and perform another action. > > > > > > > > The only way I have found to do this involves creating three different > > JMeter test plans and executing them sequentially. > > > > > > > > Is there a better way? > > > > > > > > Thanks, > > > > > > > > Mark H. Zellers > > > > > > > > -- Michael Stover <[EMAIL PROTECTED]> Apache Software Foundation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
