On 19/05/06, Gaël LHEZ <[EMAIL PROTECTED]> wrote:
Hi,

I'm trying to use the synchronizing timer which is supposed to do the
following : it wait for X threads, and then continue (eg: pass to another
test element).

For my test, I need to wait for all user, because I need them to do a
specific work, before continuing. After their work is done, I will do a long
task, and then those users will do another work.

Supposing the first task is Task 1, long task is Task 2 and last task is
Task 3, here what my test looks with synch' timer :

ThreadGroup (15)
  |- Task 1
  |- Synchronizing Timer (15)

This will apply to ALL samplers in the thread group

  |- If ${counter} = 1
  |    |- Task 2
  |- Synchronizing Timer (15)

This will apply to ALL samplers in the thread group

  |- Task 3


All timers are applied to ALL samplers in their scope.

Before doing so (since HTTPS does not work on my test, I can't do real
test), I tested juste the synch' timer with the following test :

ThreadGroup (15)
  |- Counter (1 -- > 9999999)
  |- Login
  |- Synchronizing Timer (5)
  |- Test Sampler (named 'coin coin ${counter}'

Here is the result :

1       [log=1]
...
8       [log=3]
9       coin coin 1
10      [log=2]
11      [log=5]
12      [log=6]
13      coin coin 2
14      coin coin 4
15      coin coin 3
16      coin coin 5
17      [log=10]
...
21      [log=6]
22      coin coin 6
23      [log=7]
...
26      [log=10]
27      coin coin 8
28      coin coin 7
29      [log=11]
30      coin coin 10
31      coin coin 9
32      [log=13]
...
36      [log=11]
37      coin coin 11    31      true    13015
38      [log=13]
...

1. I don't understand why coin coin 1 come before the other samplers?
2. The test does not even stop !

Curiously, stopping the test force the 'coin coin 12 to 15 ' to appear

I don't know if the synch timer is buffy or not, but it does not seems to
work.

See above.

Also, i'd like to know if I could do the following (with the same approch in
mind) :

Thread Group (1)
  |- Thread Group (15)
  |    |- Task 1
  |- Thread Group (1) (wait previous thread group to end)
  |-   |- Task 2
  |- Thread Group (15) (wait previous thread group to end)
       |- Task 3


Thread Groups cannot be nested.

Last time I tested that, the parent thread group ignored the inner thread
group (like if there was Simple Controller).

What should/could I do ?


There is some information on scoping in the JMeter documentation.

I suggest you use the Java Request Sampler to create a simple test
plan so you can try the features out without needing a server.

S.

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

Reply via email to