russp

 Profile Answers by russp 

• May 12th, 2009

 

In relation to the effort required to maintain a script in terms of programming overhead, fewer scripts = less work.  However multiple actions within a single script can reduce its portability.  (i.e., you'll be less likely to be able to reuse it in a different situation.) 

In relation to the analysis of the application itself, a variety of actions better simulates real-world conditions.  For instance, hammering the server with all database lookups may certainly find a bottleneck in that area, but may not be representative of a real-world load. 

It depends on what you are trying to achieve then.  How it scales in the real-world? Or pin-pointing a bottleneck in a certain area?

patu_ctc

 Profile Answers by patu_ctc 

• Nov 18th, 2009

 

It all depend on you, for example you are creating few orders and you need to book that order and for this requirement you are using two different scripts.

Instead of doing this you can simulate both this transaction (creating order and booking the order) into a single script with two different actions where you can create the order and and also you can book the order simultaneously.