Need source control advice for TestComplete projects
I am fairly new to TestComplete, having completed a short evaluation. As my team embarks on a more systematic use of the product to automate tests, we want to get the work under a source control system. Do you have any advice or support for this?
Our organization uses Mercurial for product source code. I see that other SmartBear products (e.g. AutomatedBuild) document support for integrating with Mercurial. Is it possible that some of that technology has been or could be made available for integrating TestComplete with Mercurial? Can you provide any whitepaper on how best to use Mercurial to control TestComplete projects under development, whether integrated into TestComplete or not? [E.g. What files are necessary, specific caveats about dealing with replicas that may change the test root directory, etc.]
Any advice to get me a good start on this will be well-appreciated!
~Douglas
Our organization uses Mercurial for product source code. I see that other SmartBear products (e.g. AutomatedBuild) document support for integrating with Mercurial. Is it possible that some of that technology has been or could be made available for integrating TestComplete with Mercurial? Can you provide any whitepaper on how best to use Mercurial to control TestComplete projects under development, whether integrated into TestComplete or not? [E.g. What files are necessary, specific caveats about dealing with replicas that may change the test root directory, etc.]
Any advice to get me a good start on this will be well-appreciated!
~Douglas
