I have to perform a load test manually with 20 people, the time cost of scripting this is too prohibitive and the application being tested (tridion) doesn't lend itself to easy scripting.
So I'm coming up with a simple plan and wondered what people thought.
- Script: A simple list of actions I want the users to perform. It's a high level list because I want the users to do things their own way instead of following "click here.." type instructions. We want this to be realistic of a production day.
- Data: I'll provide any sensitive data but mostly whatever people can think of is fine. I might need to specify minimun lengths to prevent peole typing "asdasdafs" for everything.
- Time: I think no more than 10 minutes. Some quick people will do the script twice in 10 minutes, but that's ok.
- Measurement: We'll get subjective view from users about any performance problems. We'll also get an objective view from the server by recoding the "time taken" extended attribute in the IIS logs. Finally, we'll have performance monitor logs.
- Repeatability: It'll be impossible to repeat the test exactly, and may be difficult to repeat at all because people won't be so keen to help the second time, but we're stuck with this method.
I'd welcome your comments, thoughts.
Everywhere's within walking distance if you have enough time.
1. That the scripts represent most-critical daily processes and consist of the most critical transactions.
2.1 Is realistic and/or
2.2 Is such that it triggers exception processing encountered daily - such as user/member privilege levels, etc.
2.3 If you can get away with a data or naming convention, use one. Example: When filling out a form - manual tester one uses "Manual 01" in first/last name, comment fields, etc. This facilitates below 5 and removal of database records should you require such.
3. Provide the participants with a spreadsheet template. I have attached a two-sheet XLS file to this post header if you wish.
4. Include server(s) monitoring.
5. Repeatability: You can get a feel for this from the logs or a tool such as WebTrends, and - use that data later for automation or more of manual.