R. E. Cook
Contact Us 

Dr. Cook

RunningShoes Library for WinRunner 

Custom WinRunner Functions 
and Utilities,
to Your Specs

A Random Collection of WinRunner Solutions

Creating DLLs for WinRunner 
"DLLs Demystified" 
(Mercury Interactive's Worldwide Users Conference 2000)

R. E. Cook Consulting


Handy utility scripts using RunningShoes

This is a collection of scripts written to perform various utility tasks for specific clients in need. We're making generic versions available just in case they may be useful for others with similar needs. They also illustrate different uses for the RunningShoes library. Feel free to edit as desired for your needs. We'll be adding to this collection as we get generalized scripts documented.

NOTE: These scripts were developed for perfoming specific one-time tasks that are not directly involved in testing. They were meant to get a job done. Therefore, although they have been cleaned up enough to be presentable, these scripts are not polished by any means. You will find practices in these scripts that would not be acceptable in a finished product, such as lines of code that have been commented out but not removed, as they should be. We present these scripts as is, in the hope that someone might find something of value in them.

Easily add functions to the function generator

Faced with the daunting task of adding the nearly 400 functions in the RunningShoes library to the function generator, we of course devised an automated function generator process to do the job. The functions are described in a simple input file set up as a standard configuration (.ini) file. This script reads that input file and converts the function descriptions to the convoluted statements needed for the function generator. The output can be pasted into a WinRunner script, which can be executed when you need the functions in the function generator. 

The process and the input file are described in detail in the script header.

Compare WinRunner scripts

Lack of real version control integrated with the tool can lead to total chaos with script proliferation. A recent client had a serious problem with a few hundred WinRunner scripts, repeated in three different folders. Testers edited scripts in various folders without regard to keeping one folder current. We wrote a script that looked through all the tests in one folder, comparing the scripts to tests with the same name in the other two folders. The client was then able to sort through the file comparisons manually – still a small amount of manual work, but far less than doing it all manually, since the comparisons were created programmatically.

Here's a simplified version of that script. This version compares test scripts in two folders containing automated tests. It performs a file comparison on the script files in any pair of folders with the same name. It illustrates capturing an array of all first-level subfolders of the target folder, then looping through those subfolders to compare the script file in each.

The script is presented here as a text file to avoid browser format mangling. View the WRScriptCompare script as a text file.

Updated 9 December 2005

Top of  This Page | R. E. Cook Home Page

Copyright R. E. Cook Consulting, 2000 - 2011.
All rights reserved.

The site is designed to look best when viewed with Internet Explorer 5.0 - 8.0. Results with other browsers will probably deviate from what is intended.

NOTE: This website refers to registered trademarks and service marks that are owned by other companies, including Mercury Interactive, WinRunner, TestDirector, TSL, Microsoft, Windows.