Thanks a lot for the useful checklist.

I would add 2 tips:

- test data/test users for the script is/are set up
- The script related information is documented in a specification

Generally I don’t worry about getting multiple errors when a single page fails, as most of the time I get duplicates anyway as a web_reg_find() will fail as well as a Content Check Rule (if it is a known error message), but testers should definitely not be using web_reg_save_param() failing to do their error checking for them.

I would be keen to link to your checklist if you post it on your blog. :)

Cheers,
Stuart.

It’s a shame what is happening, but I still believe if you are passionate about your work you will still do very well.

I like this list also, I too constructed a similar list, however, I’d like to make a slight contribution to your list.

web_reg_save_param to have “notfound=warning”, and to allow the web_reg_find to do the error capturing, or you will get duplicate errors in controller, and many errors when a page fails, also, as part of runtime settings, that the ‘continue on error’ is not checked, to stop a domino affect on errors.

Cheers.

In this case it was a contractor who had claimed to be a LoadRunner expert on their CV, and had been brought in to help with load testing during the final 6 weeks of a short project.

It quickly became obvious that the contractor did not have even a basic understanding of C, and they had never created a VuGen script for a web application before.

He was quickly sent back to the recruitment company who had provided him.

The funny thing was that I ran into him a week later. He had been hired by a different project at the same large Australian retailer.