It's been awhile, but XRunner is practically identical (functionality-wise) to WinRunner. I believe we had more installation/setup trouble with XRunner, but once it was working things were very much the same. I don't think you would have any trouble using XRunner if you are familiar with WinRunner. I can't recall any differences between the two, other than the Unix/Windows environment.
The GUI Map functionality will be different in XRunner than WinRunner and you will probably have to "relearn" the GUI when you move to UNIX.
Also, XRunner is generally one release behind WinRunner (& that's from a Mercury rep).
We are using winrunner and xrunner on sloris. Xrunner doesn't support browser lervel actions.
check the below message
XR - WR PORTABILITY...EXPLAINED
"Porting WinRunner scripts to XRunner is a functionality that the products are currently not designed to seemlessly do.
However, it can be done." There are basically 3 issues with XRunner - WinRunner compatibility.
XRunner is equivalent to WinRunner 4.0, so all new features, functions, etc from WinRunner 5.x and 6.x don't work in XRunner.
Trying to run a WinRunner script in XRunner is like trying to take a WinRunner 6.x script and opening it in WinRunner 4.x.
1) Header file The formats are no longer the same. You can also just delete the header file as long as it isn't a compiled module.
2) GUI Checklists The formats of the GUI checklist files and results has totally changed. As of now, there is no resolution for this issue other than to recreate the checklist on XRunner.
3) Functions All of the newer functionality (like virtual objects, database functions, etc) do not exist in XRunner.
4) Differences between XRunner and WinRunner - No need to explicitly link libraries to applications in WinRunner, this is done by way of DLLs. -
No virtual object support in XRunner- the Virtual Object Wizard is not available.
- No HTML support or WebTest Add-In as it is referred to in WinRunner.
- No need to explicitly open and close a file in XRunner.
- File I/O is not available and not needed (ie- file_open is an undefined function).
- No Add-In Manager. - Different applications or ToolKits are tested by setting the environment variable MIC_TOOLKIT.
- License Keys must be installed for certain functionality- Context Sensitive recording and Text Recognition- controlled by a License Manager.
4) Other - Files in db directory (tm.asc, crvx.asc) are platform dependent and will need to be recreated- just copy the script file over and save the script to re-create this db directory. - GUI Maps- objects/windows contained in the GUI file may contain differences in their physical descriptions (Java may be an exception to this) - Unix and Windows identify directories differently, Unix uses a / and windows uses a \ - No spaces are allowed in Unix directory names - Bitmaps are not portable - A good way to determine Xrunner vs. WinRunner is by the OS with a TSL function GUI_get_name(out_name, out_version);