Forum Discussion
4 Replies
- tristaanogreEsteemed Contributor
What do you mean by "collaborate"? QAComplete, with my limited understanding of it (which I don't have much experience, to tell the truth) is more about scheduling test runs, defining manual tests and tasks, and co-ordinating those efforts. While there is some aspect of that involved in "collaboration", it's not exactly working together on scripts.
This is why automated test development needs to be treated, in many ways, as any software development project/process. In those processes, "collaboration" is done via source control tools like TFS, Git, Mercurial, SVN, etc. This way, one person does some development, another modifies etc., and everyone's changes get to everyone together.
Is this what you mean?
- efullerOccasional Contributor
Hi Robert,
Thank you for your reply. In regards to TestComplete I was leaning towards Source Control being the answer.
With QAComplete however, we can push TestComplete tests to QAComplete and have them be ran by a host machine on a schedule, which is great. But I can't find any solution/answer as to what happens to the automated tests in QAComplete when a change is made in TestComplete. There doesn't seem to be any update/sync features that I can see happening, so I was hoping someone can tell me I'm wrong and that feature is already built in, or any solutions they've come up with.
- tristaanogreEsteemed Contributor
I'd hate to think something like that would be missing in the integration between the two tools... that is, unless it's a moot point. But then, I'm not as familiar with the QAComplete tool. Perhaps this is a question that could be posted to the QAComplete forums as they may have a better pool to answer from (https://community.smartbear.com/t5/QAComplete-and-ALMComplete/bd-p/QAComplete).