| || |
Run Automation on New Machine. Automation Function Library,OR and Test Script present
Consider machine 1 with the following folder structure :
Now I want to run the automation on Machine 2.
Question 1 - How can we run the automation from Machine2.(Pls share the sudo code for this)
Question 2 - Can we write a script, for the above situation.
Now I want to run the automation on Machine 2. --- On Machine2
Question 1 - How can we run the automation from Machine2.(Pls share the sudo code for this) -- From machine 2
Confuse , So you want to run test on second machine after copying code from machine 1 , or call test on machine 1 from machine 2 by remote connection?
Well depends on network privileges, but you could access the scripts on machine2 with \\machine1name\d$\. Not sure what license structure you have, but if running scripts on both at same time or you just have a seat license, machine2 would need a second license.
Scripts would be better suited to live on a shared network drive or in a version control system and checked out locally.
Seat licence is per seat. Concurrent licence , let you install UFT on many machine but keep activate n-numbers from that pool based on the licence.
Evaluation licence is the little brother of Seat licence and live with you for 30 days.
So if you have concurrent licence , you can run same tests. As NoUse4aName ( well there may be a use for THE name) suggested , shared drive is what most people go with apart from QC.
@Thanks for post Yogi. I guess I have not put my question correctly.
When automation was created we have used Machine 1 for all the development purpose.
Now a Client OR may be a new user who has Machine 2 and QTP installed on it. Now he wants to run the automation . How this can be done.
What script can be written so that a new user with QTP on his / her machine can use and run the automation.