newbie23
14 years agoOccasional Contributor
TestComplete problem in Automated Build Studio
Hello,
I have a macro in Automated Build Studio that first builds a vb6 program and then runs a test on it in TestComplete.
When I run this macro in Automated Build Studio, all is well. However, if I set up a Continuous Integration task to run this same macro, TestComplete fails to find the initial object. It appears (based on some of the debugging I did in TestComplete) that TestComplete and the program it is opening are both running invisible.
To try and work around it, I also tried to have Automated Build Studio open the program and then have TestComplete take it from there. Automated Build Studio also opened the program invisibly and although TestComplete was still running invisible as well, it gave me the error I was looking for: "The window is invisible and thus cannot be actived".
So it appears the problem is that either way I go, my program opens invisibly. I don't see any options in the CI Task scheduler to change this, so how can I fix this?
I have CI task set to run whenever there is a svn update so ideally it will do a build and then run regression tests along with new unit tests that get added to the script.
Any idea's?
I have a macro in Automated Build Studio that first builds a vb6 program and then runs a test on it in TestComplete.
When I run this macro in Automated Build Studio, all is well. However, if I set up a Continuous Integration task to run this same macro, TestComplete fails to find the initial object. It appears (based on some of the debugging I did in TestComplete) that TestComplete and the program it is opening are both running invisible.
To try and work around it, I also tried to have Automated Build Studio open the program and then have TestComplete take it from there. Automated Build Studio also opened the program invisibly and although TestComplete was still running invisible as well, it gave me the error I was looking for: "The window is invisible and thus cannot be actived".
So it appears the problem is that either way I go, my program opens invisibly. I don't see any options in the CI Task scheduler to change this, so how can I fix this?
I have CI task set to run whenever there is a svn update so ideally it will do a build and then run regression tests along with new unit tests that get added to the script.
Any idea's?