Forum Discussion
AlexKaras
Champion Level 1
14 years agoHi Dale,
Sorry for the non-positive opinion...
As Mike already said, all integration with TestComplete is done on the devTest/devSuite side. I don't know its current state (hopefully, it improved), but when we evaluated integration with TC7.52 approx. 18 month ago, we were not satisfied with how it was done.
The major problem, as far as I can recollect, was the fact that when you marked test in devTest as automated, the only option available was to specify the whole TestComplete project as a test target. No chance to specify test item or script routine, just a whole project.
At that time we already had several TestComplete test projects and every test project had a structured tree of test items. Definitely it was near to impossible for us to create a separate test project for every test just to be able to execute it from devTest.
Another thing (it might be not 100% correct, so you should double-check this) was that it was not possible to specify in devTest the required order of tests execution. We needed this because some of our functional tests were dependent on the previous ones and provide input data for their child test items. I.e. for example, you cannot test the payment procedure while the order was not made and it is impossible to generate the report until the payment was not done. While this can easily be organized via test items in TestComplete, the exact order of tests execution is required in devTest to guarantee the correct sequence of performed actions.
AFAIR, these were the major cases that prevented us from integrating TestComplete with devTest.
Sorry for the non-positive opinion...
As Mike already said, all integration with TestComplete is done on the devTest/devSuite side. I don't know its current state (hopefully, it improved), but when we evaluated integration with TC7.52 approx. 18 month ago, we were not satisfied with how it was done.
The major problem, as far as I can recollect, was the fact that when you marked test in devTest as automated, the only option available was to specify the whole TestComplete project as a test target. No chance to specify test item or script routine, just a whole project.
At that time we already had several TestComplete test projects and every test project had a structured tree of test items. Definitely it was near to impossible for us to create a separate test project for every test just to be able to execute it from devTest.
Another thing (it might be not 100% correct, so you should double-check this) was that it was not possible to specify in devTest the required order of tests execution. We needed this because some of our functional tests were dependent on the previous ones and provide input data for their child test items. I.e. for example, you cannot test the payment procedure while the order was not made and it is impossible to generate the report until the payment was not done. While this can easily be organized via test items in TestComplete, the exact order of tests execution is required in devTest to guarantee the correct sequence of performed actions.
AFAIR, these were the major cases that prevented us from integrating TestComplete with devTest.