On 20/05/2010, Carsten Wolters <[email protected]> wrote: > > > Hi all! > > I'm currently evaluating JMeter if it meets our requirements for > distributed functional tests. I read many documents, FAQs etc but there was > no answer if JMeter is able to solve the following distributed functional > test setup. Involved are four PCs (PC1-PC4) and the JMeter client managing > the remote instances (C). > > C starts the test plan which should be executed step by step (not in > parallel on multiple PCs!): > > > PC1 starts a process generating some data and injects it into a work flow > that subsequent generate some data artifacts on PC2-4: > > PC2 checks if a log file has been written > > PC3 checks if a file has been created (but only if step 2 has not failed!) > PC4 checks some data in a database (but only if step 3 has not failed!) > > PC1 get the result of the test-injection and asserts the result if necessary > (but only if step 4 has not failed!) My core question is: how do I write a > test plan so that JMeter executes only specific action(s) on one specific > PCs and how is synchronization done between the distributed JMeter > instances? > Is the JMeter client instance able to synchronize multiple remote JMeter > instances at some test step?
In client-server mode, JMeter runs the same test plan on all the servers at the same time. So the only way for the servers to behave differently is to code the test plan using some conditional logic. This can be tricky to get right unless the test plans are fairly similar. You don't say if PC1 continues processing after it has created the data. If not, then just use a shell script to run first PC1 then PC2-PC4 then PC1 again. It sounds like the test plans are probably very different, in which case I would suggest creating independent tests that run on each PC. There's still the issue of synchronisation. You can use one of the BeanShell test elements to run some Java code to wait for the file to be created. Similarly for other conditions. > Thank you for your patience! > Carsten > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
