Customer lost some data due to no lock
Sometimes, locks are not done. I mean : user A is modifying class module X user B try to open class Module X => It works, then the last user who save won... !
They are using TestPartner 6.2 latest build.
For the database they are using SQLServer 2005 SP2.
They are experiencing an issue with concurrent access management on TestPartner class modules.
Sometimes they are 2 people working on the same TP class module and the last one who saves its changes got them applied in the TP SQL Server db, while the other one looses its changes. Another issue with the class modules is that sometimes TP can't close class module saying another machine is using it while this is not the case.
We did a webex with the customer with the following results:
Customer has VMs running TP 6.2 b449 in XP SP2 that access a served db. User1 on VM1 opens moduleA and edits it, while that is open User2 on VM2 opens the same moduleA with no warning. VM2 can edit moduleA. When VM2 tries to save moduleA, sometimes they get no warning that it is locked, sometimes they get a warning that it is locked by User1 on VM1, sometimes they get a warning saying that it is locked by "" on "" - no user or machine. This happens whether they open the module via the Asset Browser or via the Definition option in a Test Script.
When User1 on VM1 opens a test script, if User2 on VM2 attempts to open the same test script, they get a warning immediately.
Database is SQL Server 2005
If somebody knows how to handle this problem that would be very helpful!
Re: Customer lost some data due to no lock
I've never ran across this, It should limit the module edits like the script edits. If it isn't you might want to submit this as a bug.
Work Around: Duplicate the module for each user instance so they can edit all they want and at the end of the day perform a merge. There are plenty of tools that support text/code difference merging capabilities so it shouldn't be too painful of a process unless everyone edits the exact same lines. Limit the master module to only be editable by one or 2 people so only those people can update the changes for everyone to use.