loadrunner Hi, is it a good practice to make different...

[Aritra Das]

Hi, is it a good practice to make different actions for each and every transaction in the time of recording the scripts?

 

[Shane Evans]

No, just for every business process that can be reused. Most transactions are a subset of an entire process, but you can create an Action for a self contained business process that can be called from other scripts and build more of a framework around your scripts.

 

[James Pulley]

No. I typically take this as an indicator of someone who should be replaced for creation of a maintenance burden on the code moving forward. When observed this is also typically paired with really bizarrely complicated scheduling models with even the attempt to reproduce 100% of the data flows in a given time period (including a transaction type that occurs as few times as one per hour). This is also a prime indicator that the stakeholders of the performance group are not the business stakeholders but are more likely development and/or operations who are pushing for 100% edge case validation.

 

[Raymond Lorenz]

I agree. I rarely use more than one action. I rather have more scripts. Quicker/simpler. The only time I use more actions is when I need login sessions to be shared or minimized. What I do try to do is create a transaction for each server call. Even if I don't include it in the reports.