LoadRunner脚本评审Checklist

LR脚本应该像软件的开发代码一样进行适当的评审和检查，防止脚本开发的各种错漏，为此建立一个Checklist是个好办法。

参考：
http://performancecheck.blog.co.in/2008/08/11/script-development-checklist/

If you are pretty new to scripting with LoadRunner VUGen, chances that you will miss one or two important steps, that may be missing out of the think time settings, number of iterations, insufficient parameters, location of load generators, areas to encompass a transaction, etc… Therefore, it will be a good idea to have a checklist to keep track of the things done for each script….

TEST PROJECT: LOADRUNNER ADMINISTRATOR:
{project name} {LR admin name}

Script 1

Real-time think times? X
Check strings inserted in the script? X
Parameters defined? X
Are data files complete (incl userid/passwords)? X
Correlation complete? X
Exceptions handled? X
Are script set to run multiple iterations? X
Comment header block included? X
Comments within the script? X
Start/Stop transactions defined? X
Start/Stop sub transactions defined? X
“Are the scenarios designed to meet real time execution?” X

 

当然，如果做了这样的检查，然后还是出现了错误，则需要调试和定位错误，可以采用这篇文章所介绍的系统化的分析方法来进行：
http://www.loadrunnertnt.com/errors/why-are-my-scriptsvusers-failing/

问题可能出现在VUGen，那么可采用下面分析步骤：
1. The application that you are replaying against is not running.

2. There were changes to the application 

3. There are dynamic values that needs to be correlated.

4. The parameterization may be causing the problem
For (1) to (4), it’s recommended to turn on Full Extended Log (all options enabled: Advanced Trace, Parameter Subsitution, Data Returned From Server) in the Runtime Settings (Vugen) to verify the data that is been transmitted between the server and the client (script). Through this, you can find out what and where that could have gone wrong in the replay.

 
问题可能分析出现在Controller：

5. Does it happen at the start of the scenario execution?
If the script/vuser fail at the start of the execution, verify the script again in Vugen

6. Does it fail on a particular Load Generator (LG)?

7. Does it happen at the middle of the scenario execution?
When this happens, the Application Under Test (AUT) maybe under load and unable to process all requests from the scripts/vusers and therefore returning errors to them.