#FUNCTIONS IN WINRUNNER FULL#

#FUNCTIONS IN WINRUNNER FULL#

We decided to create a more robust version of our utility that would allow full editing, and Function Manager was born. There was only one problemвЂ¦ you still had to edit your files in WinRunner. You could browse all of your compiled modules and Function Browser would parse out what was available and even provide a code viewer. We published this utility as a download on the Mercury support website, and it quickly became one of the highest rated tools you could download (along with our stand-alone GUI Map Editor utility).

Keeping up with those libraries was the inspiration for one of our first software toolsвЂ¦ Function Browser! In those early days, functions were king! Libraries of functions were amassed in вЂњcompiled modulesвЂќ, and you had to create special startup scripts just to load all of those libraries to make them available for your tests. Being specific to WinRunner also meant you would not find much, if any, third-party support for the language. While based on ANSI C, it was still unique in the market. To show how far we have come, that was the first version of WinRunner to support syntax highlighting of keywords! WinRunner was a powerful automation tool, but used a proprietary language called Test Script Language (TSL). I began my career in test automation when WinRunner 6.0 had just been released. Our Test Design Studio product of today exists only because of the early days using WinRunner. Today marks the end of Mercury/HP WinRunner support in Test Design Studio, and the end of era for our products.

Functions in winrunner