I think TP should allow using multiple scripts at the same time and allow parallel testing. We had this discussion before and I did state this before that using an Automation Test Tool should allow parallel testing otherwise the tool is missing a great advantage.
No I am not talking about Parallel on the same machine I am talking in respect of Global use. for example if I have script call InstallLmExe, which allows you to install application on your local machine. If I want to run this script on more than one testing machine at the same time, Test Partner complains about it (file is in use by other user).
NOW:- I have plan to develop a code which allow you to install application on remote machine(s) but this requires plenty of effort that I cannot offer due to my test planning.
You CAN do parallel testing, on different machines. TP handles that very well.
[ QUOTE ]
We had this discussion before and I did state this before that using an Automation Test Tool should allow parallel testing otherwise the tool is missing a great advantage.
[/ QUOTE ]
You are right - we have had the discussion about running the SAME script on multiple machines at the same time. How is TP to keep the log straight? There is more to this than just the ability to "unlock" the script to allow multiple users to run it at the same time.
The workaround is to make a copy of the script. Then you can run the original on one machine, and the copy on the other.
Also, since we are not trying to use TP to do any sort of load testing, please explain what you are thinking when you say that TP is missing out on a great advantage. Exactly what is the advantage that it is missing out on? I'm not saying that to be cynical - I truly want to know what I am missing.
[ QUOTE ]
please explain what you are thinking when you say that TP is missing out on a great advantage.
[/ QUOTE ]
Advantage which is missing is to allow a script execution on multiple machines at the same time.
The application I work on is a network management tool which means that the application is supported on all Server OS, now if I want to test Installation of the application on 5 different machines which as 5 different OSs, I cannot run One script to perform at the same time on different machines. Iíve installed TP on each machine and then I attempted to execute one script (LM_Installer) on each machine but ones I try to execute the script on the 2nd machine the message is displayed stating "Script is in use by other user etc". I understand that you (DSquared) said make number of copies of your script but this is more work and taking more space for doing one job. I have 20 script files x 7 machines = 140 script files in order to do one job and the number of scripts can exceed when the number of machines exceed. Thatís where TP has lack of advantage for not allowing one script to do a job on different machines accessed at the same time by same user (or different user).
So far I have not managed to make it work the way I wanted according to above statement.
Isn't that what QADirector is for? I'm not saying run out and buy QAD but I'm pretty sure that's what it does.
Have you tried something like pushing out a batch job to all the machines? That may work. I believe the problem is that you cannot open a script from the GUI and replay it if someone else is executing but you should be able to from a command line.
We do have QADirector and I faced similar problem and for some reason I was fail to execute a script on number of machines via QAD, But I am not saying that QAD is doing some thing wrong may be it is me but I came to this understanding that TP does not allow to access a file more than once at the same time to be executed on number of machines.
Well nice hint Chief I might spend some time on QAD to see if it does what I am looking for
I just tried this as a test on two different machines using the command line and didn't have any problems. I also ran it from the GUI from both machines and had no problems. The only difference through the GUI is that the second user had to open the script as read-only.
Maybe the problem has something to do with your logging options. I used save as new run number when I tried it. Maybe the version of tp might make a difference, I'm using 6.1. Also could be the number of concurrent licenses that you have for TP, but your probably already aware of that limitation.