Another downside is the need to create separate scripts for the different applications. (This was true for the versions we used for a couple years. I can't speak for the current versions.)
The scripts we created in LoadRunner couldn't be used in WinRunner and vice versa. It's obvious the two applications are designed for different purposes, but for someone exploring their options, it might not be immediately apparent that they'll need to duplicate effort on building scripts AND those scripts use different grammar, thereby bumping up the learning curve.
The end result was 2 QA Engineers dedicating their lives and services to maintaining the scripts that were supposed to help alleviate the constant burden of manual testing.
Slashdot Mirror
Another downside is the need to create separate scripts for the different applications. (This was true for the versions we used for a couple years. I can't speak for the current versions.) The scripts we created in LoadRunner couldn't be used in WinRunner and vice versa. It's obvious the two applications are designed for different purposes, but for someone exploring their options, it might not be immediately apparent that they'll need to duplicate effort on building scripts AND those scripts use different grammar, thereby bumping up the learning curve. The end result was 2 QA Engineers dedicating their lives and services to maintaining the scripts that were supposed to help alleviate the constant burden of manual testing.