Forum Discussion
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.
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.
- tristaanogre5 years agoEsteemed Contributor
TestExecute is the same "engine" as TestComplete, only without the debugging and development environment. Anything you write and run in TestComplete can be run in TestExecute as a command line. So, I don't foresee any problem with you vetting it on a functionality level... it would simply be on how you would implement it in your environment.