TestComplete and SVN
Hi everyone
So I tried integrating SVN into testcomplete, and followed the instructons here
http://support.smartbear.com/viewarticle/29318/
Modifying the installation failed and give me an error which I found out is a bug. My colleague managed to get it installed and it is way too slow
http://smartbear.com/forums/f81/fp107/t66157/extremely-slow-synchronization-with-subversion
So we came to the conclusion the way to go was through the SVN client itself.
We have TestComplete 9 and Tortoise SVN.
I have already read all the articles on teamwork and sharing projects etc but I am still having problems.
I tried the svn:needs-lock property which I applied to my KeywordTest folder fine.
The KeywordTests folder is Read only now unless you obtain a lock for a KDT.
But users can still check the KDT's out and edit them, it is not until they go to save them that they now there is a lock on the KDT. Is there anyway in TestComplete to make the tester aware that there is a lock on the KDT besides having to go in to repo-browser and check?
It seems a bit useless if the file is read-only but a user can still make changes (not commit) but they would of still wasted there time making changes as they cannot save or commit
Any advice at all is welcomed :)
So I tried integrating SVN into testcomplete, and followed the instructons here
http://support.smartbear.com/viewarticle/29318/
Modifying the installation failed and give me an error which I found out is a bug. My colleague managed to get it installed and it is way too slow
http://smartbear.com/forums/f81/fp107/t66157/extremely-slow-synchronization-with-subversion
So we came to the conclusion the way to go was through the SVN client itself.
We have TestComplete 9 and Tortoise SVN.
I have already read all the articles on teamwork and sharing projects etc but I am still having problems.
I tried the svn:needs-lock property which I applied to my KeywordTest folder fine.
The KeywordTests folder is Read only now unless you obtain a lock for a KDT.
But users can still check the KDT's out and edit them, it is not until they go to save them that they now there is a lock on the KDT. Is there anyway in TestComplete to make the tester aware that there is a lock on the KDT besides having to go in to repo-browser and check?
It seems a bit useless if the file is read-only but a user can still make changes (not commit) but they would of still wasted there time making changes as they cannot save or commit
Any advice at all is welcomed :)
