This is an EXTREMELY common request. As a matter of fact, the ability to do this is often a big "point" made to management to get them to approve the expense of automation.
There are some previous posts about things not working the same (as NT) or at all on Win95, Win98, W2K. Check those out.
If you didn't plan for this then you will likely run into OS-specific problems such as syntax when dealing with the registry, folder/filenames, manipulating an OS tool such as Explorer, Acrobat Reader, NotePad, etc. The list could be huge.
My suggestion is tackle it in phases. Don't start "fixing" as soon as you find one problem. Handle any biggies of course (issues that prevent anything from running or impact a big hunk of your scritps) but then try to get through one run of ALL of your scripts on each of the other platforms. Then you'll have enough info to actually plan the "fixing" part.
Our Automation Group has been asked to run our scripts against our AUT on multiple operating systems (Win95/98/ME/NT/2K)? Is this a common scenario and if it is, what problems can we expect to run into?
As earlier post says may be issues related to rgistry keys and path names. My suggestion if you are having more constants declared for reg keys and file names and their paths maintain different include files specific to OS and use them accordingly.
Your base code of tetsscript file should work fine. Only issue is do not hard code file names and file paths instead create a include file and declare them as constants differently for different OS. Hope this helps you.
I don't agree with sree about the separate include files for each OS. It is easier and more maintainable in my opinion to just conditionally code around the minor differences between OS's. You also don't have to worry about which inc file you are "using" all the time. SilkTest provides the guitype statement or the GetGuiType function that should be more than enough.
To add to MattGray's reply:
We use GetGuiType() and conditional statements like mswnt, msw98, msw9x.
Also, we use environment variables on the system to figure out windows dir, windows system dir, temp dir, and the registry to look up other things.
Environment vars that are helpful:
<LI> COMSPEC path to command.com on 9x, or cmd.exe on NT
<LI> TEMP path to temp directory
<LI> WINDIR windows dir
get system dir by appending \system for win9x, or \system32 for winnt[/list]
Scripts can rely on getting this kind of information at runtime, so you don't have to have separate hard coded include files.