WinRunner - add in problem
I am using winrunner 7.5 and web based test director.
I want to use PB(Power Builder) Add in.
When I run the script from TestDirector, It launches and run the win runner script with VB and Active x as addins and the script failes.
I edited the wrun.ini file for PB addin and then I run the Testdirector, it uses the VB and Active X addin.
If I use startup script on winrunner setting, I need to do the same for all remote machines what I planned to use. Right??
So any ideas/clues to solve this.
Thanks in advance.
Ramesh Babu Meda
Re: WinRunner - add in problem
use a run line command that points to a shared .ini file with the correct environment info - then just copy the adjusted .ini file out to a shared drive and set up all WR enabled machines to point to the shared .ini. Or you could just set up WR to not load any add-ins at start up time - then have the initial "test" in your test set call to the ad-in script that is needed. Fo example - you cold have a script call the pbinit script located normally at: C:\Program Files\Mercury Interactive\WinRunner\lib\pbinit - and let it do the initialization at that time.