The AUT Default Path appears to be reset to the path of the current script being run. The AUT writes output files that do not register in the proper and expected physical directory.
Windows NT SP6, WinRunner 6 plus 6.2 patch.
AUT is on drive D:
Mercury is on drive E:\Program Files\Mercury Interactive\WinRunner
Scripts (Over 200) are also on drive E:\wr\folder1\folder1
AUT output is being placed on drive E:\wr\folder1\folder2, not drive D:
search path for called test is set to drive D:
Note that I could use the AUT File-SaveAs but this does not represent the way the AUT is designed or shipped.
Any ideas would be helpfull.
While I have not run into this myself I am curious as to how you invoke the application?
If you are useing invoke_application are you
specifying a working_dir? If not let me suggest you do.
If you employ dos_system to start your AUT maybee you should use:
invoke_application ( file, command_option, working_dir, show );
And employ the working_dir. If this isn't even close let me know what you are doing. If this helps let me know that to. Never know when we will all get bit by something like this!
Smoke me a kipper, I'll be back for breakfast!
Sr. QA Engineer
The working directory entry solved the problem.
Sometimes I screw up the obvious, and easiest by not reading the manual closely.
Thanks Ed Anderson
"If you are useing invoke_application are you
specifying a working_dir? If not let me suggest you do."
User WinRunner (email@example.com) posted:
Can any body provide information about \"what AUT is ? and its significance.
User (firstname.lastname@example.org) posted:
AUT is Application Under Test
User Richard Weber (email@example.com) posted:
AUT is Application Under Test. The program that's getting tested.