R. E. Cook
Home 
Contact Us 

Dr. Cook
Resume 

RunningShoes Library for WinRunner 
RunningShoes 

Custom WinRunner Functions 
and Utilities,
to Your Specs
Custom 

A Random Collection of WinRunner Solutions
Solutions 

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

R. E. Cook Consulting

 


RunningShoes Frequently Asked Questions 

 

Follow the links for answers to questions someone has already asked:

Why does WinRunner give the error message RunningShoesInit not found in the search path for called tests?

Why aren't the RunningShoes functions in the function generator?

What operating systems does RunningShoes handle?

RunningShoes installation fails on Windows NT, with an MSIEXEC error.

I receive the message "The 90-day trial period has expired. Continued use of the library requires purchase of a site license."

I receive the message "This beta version of RunningShoes expired on ---. See www.recook.com for the current version of RunningShoes."

I've installed RunningShoes. Now, how do I use it?

How can I read the documentation for RunningShoes functions?

Why does the RunningShoes documentation crash on some PCs when WinRunner is open?

Can I install RunningShoes on a server?

Why can't I choose to install RunningShoes to a different path?



Why does WinRunner give the error message "RunningShoesInit not found in the search path for called tests"?

This error message has a few possible causes. 

First, make sure that RunningShoes is installed on the PC where the message appears. You can check in Window's Control Panel, Add/Remove Software. If RunningShoes is installed it should appear in the list.

If RunningShoes is installed, ensure that your search path for called tests includes the WinRunner\lib folder in the WinRunner root installation, usually "c:\program files\mercury interactive\winrunner\lib\". Set the search path in WinRunner under General Options, Folders.

If the message still appears, verify that the RunningShoesInit test exists in that WinRunner\lib\ folder. As with all WinRunner tests, it must include the script and header files, the subfolders exp\ and db\, and the 2 .asc files in the db\ folder. If the test appears to be missing any needed components, the installation has been corrupted, and reinstalling RunningShoes is the safest approach to ensuring that the installation is complete and valid.

Return to top


Why aren't the RunningShoes functions in the function generator?

We now have a beta version of a script adding all RunningShoes functions to the function generator. It has been only briefly tested, but the script will be posted here in beta form one of these days, for you to use at your own discretion.

We've been working on it, but we gave the function generator a lower priority so we could make the library and its documentation available. As an outgrowth of this effort, we now have a utility script for easing the process of adding many functions to the function generator. Instead of writing the TSL statements for each function, you can create a simple .ini file for the script to read, and let it generate the TSL statements in their arcane syntax. Look for it in the utility scripts collection.

Return to top


What operating systems does RunningShoes handle?

The current release of RunningShoes requires at least Windows 98 in the Windows 9x family, and Windows NT 4.0 SP 6 in the NT family. Setup allows installation under later versions of Windows, but RunningShoes has not been tested with Windows ME. Setup will not allow installation on Windows 95, or Windows NT earlier than version 4.0. 

Note that setup will allow installation on NT 4.0 with service pack less than 6, but RunningShoes will fail to run in that OS.

Return to top


RunningShoes installation fails on Windows NT, with an MSIEXEC error.

The Windows Installer fails to install itself automatically as part of the RunningShoes installation under Windows NT and on some releases of other versions of Windows. Installation on those PCs requires manually downloading the Windows Installer and installing it, then running either version of the RunningShoes installation. 

To install the Windows Installer, download it from the same page as the RunningShoes installer, or directly from Microsoft.

Return to top


I receive the message "The 90-day trial period has expired. Continued use of the library requires purchase of a site license."

This message means that more than 90 days has elapsed since the library was installed on the PC where this message is received. The free-trial period has expired, and RunningShoes cannot be loaded or used on that PC until a site license is purchased and installed. Please contact us to purchase a license.

Return to top


I receive the message "This beta version of RunningShoes expired on ---. See www.recook.com for the current version of RunningShoes."

On at least one occasion, we posted a new beta release without ensuring that the expiration date was set properly. If you receive this message either during use or during installation, the version is an obsolete beta version (perhaps it was obtained from another website, or perhaps you did not install it until some time after downloading it). Please go to the Members' Area and simply download and install the most recent release. It will be usable for the remainder of the trial period. We're sorry for the inconvenience!

Beta releases of RunningShoes are designed to expire in order to ensure that obsolete versions do not remain in circulation. A release version will not expire, so the library can be installed and used for the full trial period.

Return to top


I've installed RunningShoes. Now, how do I use it?

First of all, be sure to see our new tutorial series for getting started.

Once it's installed, accessing functions in RunningShoes requires only a single statement in your WinRunner script to initialize the library:

call_close "RunningShoesInit"();

After the init script has run, you call RunningShoes functions from your script just like you would any other function in WinRunner, whether it's a WinRunner function or a user-defined function:

folder = "c:\\Program Files\\";
rc = FolderListSubfolders(folder, out_array);

When you no longer need to access RunningShoes, call a second script to undo the initialization and unload everything the init script loaded:

call_close "RunningShoesEnd"();

Return to top


How can I read the documentation for RunningShoes functions?

The documentation is in a Windows Help file. You can access it several ways.

1. Installation creates a link under Start / Programs / RunningShoes / RunningShoes Documentation. Clicking that link will open the documentation. 

2. Create a shortcut on your desktop that points to the Help file, which is normally installed as 
C:\Program Files\Mercury Interactive\WinRunner\lib\RunningShoes\RunningShoes.hlp.

3. Once RunningShoes has been loaded (via the "RunningShoesInit" script), you can open the documentation by calling the function RSHelp() from WinRunner. You can put this function in an "Execute TSL" button on the user toolbar, or put the statement in a script and step on it. If you put it on the user toolbar, you might also put the RunningShoesInit script on the toolbar. Then you can call the init script and load the help whenever you need it.

Return to top


Why does the RunningShoes documentation crash on some PCs when WinRunner is open?

This is caused by an easily remedied conflict between WinRunner and the version of Windows Help used by RunningShoes documentation (WinHlp32.exe). Mercury Interactive recommends adding a single line to the wrun.ini file in the [NoBBTApps] section: 

[NoBBTApps]
winhlp32.exe=rek

Don't forget to edit the wrun.ini file only when WinRunner is not running, or the edits will be lost when WinRunner is closed.

Return to top


Can I install RunningShoes on a server?

No, RunningShoes cannot be run from a server. Several known issues prevent proper behavior when it is not run from the local PC. We are exploring the possibility of installing to a server for a future release.

Return to top


Why can't I choose to install RunningShoes to a different path?

The initialization and the ending scripts for RunningShoes must be in the search path for called tests. The simplest way to ensure that they are is to put at least the initialization script under the WinRunner\lib folder. Also, the components of RunningShoes have to know where the other components are. It makes sense to keep them all together in a single location.

If we hear a strong desire from you our users, we will address the issue in a future release. 


Updated 27 April 2007



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.