Here are 5 tips for writing LoadRunner scripts.
- Although LoadRunner’s HTTP/HTML protocol has been reliable and flexible, it’s always good to try the other protocols available in LoadRunner to identify which ones are the most compatible with the application under test. LoadRunner’s Protocol Analysis is a good start.
- Transaction names should use a naming convention which allow sorting and ordering so that the transaction summary graphs can easily show transactions in proper order.
- After recording a script, make sure to rearrange Think Times to be placed outside of transactions to avoid including think time as part of actual transaction time.
- Changing runtime settings’ Browser Cache handling and Browser’s emulation of new user can help resolving some playback issues.
- Make use of the various Description properties of functions like web_button can help in identifying the correct component to perform action on.
If you’d like to learn more about how Optimus can help your team setup or improve their performance testing, email us at firstname.lastname@example.org
Have any tips of your own? Leave them in the comments!