Forum Discussion
1) How are other source control more error prone? What have you tried and what happened?
2) Have you tried the run using TestExecute instead of TestComplete? If so, what happened when you tried?
- JASmith5 years agoNew Contributor
1) I didn't mean that other source control systems are more error prone, I meant that I would need to use a different process to include this project in source control; likely adding the project to an existant Visual Studio project and managing it through there, which has a number of problems. This is in a professional environment, I don't have the luxury of using other source control systems.
2) I haven't tried that, as I'm not familiar with that product. Is it included under a TestComplete floating license, or would that need to be licensed separately?
- Marsha_R5 years agoChampion Level 3
1) I daresay most of us work in a professional environment. There are still many source control tools available. If you are not able to choose your own, then that's another story. Perhaps you can make a case for changing to a better one.
2) Here's where you can read about TestExecute. It is licensed separately.
- JASmith5 years agoNew Contributor
1) I apologize if I offended, I didn't mean to imply any relative level of professionalism, I just meant changing source control systems wouldn't be a simple process, and regardless the issue isn't with TFSSC as a system but with how TestComplete handles projects loaded with the limited purpose of executing tests as part of an automated pipeline vs. projects loaded for a more generalized test development process.
2) From what I see, TextExecute should resolve my issue handily. it might be a bit premature, but considering the timeline on which I can vet it fully is unclear I'm going to go ahead and call this one resolved.