I'm using TestComplete 7.0 for Functional/Regression testing of my project. I have a scenario that requires two or more users accessing the same project suite file simultaneously. Though it does not necessarily opened for editing the scripts but the test execution needs to be parallely done for the same project suite, by different users.
Now, i'm able to execute the test but since different logs are generated for different users at different time periods, the project suite required to be saved before being closed. Hence if one of the users initiates the save action, other users who are accessing the same project suite file gets a promp window (screenshot attached) and so if other users clicks 'Yes' or even 'No' in the prompt window, the other users log files are either lost or being overridden by the log files of the user who initiated the save action. The manipulation of log files are not consistant in this save process since the log files remain undamaged during sometimes and its getting overridden the other times.
Hope my query is clear. Can anybody provide a better solution to avoid this clash while multiple users runs the sames project suite?
Better solution: Instead of running the same project suite off a shared drive and running into these conflicts, bring the project suite files to the local hard drives of the testers to be able to run independently and utilize a source control system (like TFS, VSS, or Mercurial) to manage the central repository of the automation code and tests.
To give common access to the log files, then, utilize log exporting features to save the log files to a network location so that there is common access to the log files without having to copy files around.
Automated Testing Evangelists
Definition expert - noun - Unknown drip under pressure