Forum Discussion

ray_mosley's avatar
ray_mosley
Frequent Contributor
11 years ago

Using TestExecute instead of TestComplete

I have developed and executed tests using TestComplete, and was recently informed that I should be using TestExecute to run my tests.  Accordingly, I modified the attached regression_64.bat file (using TestComplete) to use TestExecute instead (regressionTE_64.bat).  Execution started, but I quickly got a failure and shutdown.



I attempted to find documentation on TestExecute and TestComplete differences, but was unable to find any documentation that might account for the failure.  The failure occurred on line 1063 as shown on the .jpg attachment.



We have Enterprise licenses for TestComplete/TestExecute 9.3.



Any suggestions as to what might be wrong?
  • Colin_McCrae's avatar
    Colin_McCrae
    Community Hero
    11 years ago
    Is everything else the same?



    You're running on the same PC, same user account, etc etc.



    In other words, the only thing that has changed is updating the batch file to run TextExecute rather than TestComplete?



    You may want to check that the extensions setup is the same in TestExecute as it is in TestComplete. Don't have an install of TestExecute handy to check, but from memory, if you right click on the icon once it's started, you should be able to access options.



    I have a set of script extensions which drive my test framework for instance. If I forget to install those on a TestExecute install, it won't get very far ....
  • ray_mosley's avatar
    ray_mosley
    Frequent Contributor
    11 years ago
    SIGH!  Hate to admit this, but it was a user error.  I was depending on my memory (first mistake). After the install of TestExecute, it did not get set to "Run as administrator" (second mistake).
  • ray_mosley's avatar
    ray_mosley
    Frequent Contributor
    11 years ago
    There was not any real information in the log, but what I have is attached.



    Thanks for your time.
  • Colin_McCrae's avatar
    Colin_McCrae
    Community Hero
    11 years ago
    Heh. Things like this are often simple user oversight. Done it plenty times myself. :)