Forum Discussion

valentine's avatar
valentine
Contributor
14 years ago

TestExecute: Catastrophic failure

Hello,

I am having a problem with an error message that keeps popping up each time I shut-down TE.

I have the below line of code in a '.cmd' file that executes continously.

When ever I colse the cmd window and EXIT from TE, or sometimes when the project opens and restarts, I get the same error:

"An error occured while detaching from TestComplete

Catastrophic failure"...



script:



echo  Stay in Testexecute: RegressionTest

:loop

"C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" "C:\TestComplete\TargitAppi\TARGITTestSuite.pjs" /r /p:TARGITRegressionTest /run /exit

GOTO loop



I am running : Testcomplete 7.52.678.11

machine: Microsoft Windows Server 2003 Enterprise Edition Service Pack 2



NOTE. I run the same scripts and cose in "Microsoft Windows XP Professional Service Pack 3", and it runs smootly with NO errors.


  • NOTE:

    Made and error on the machines.



    I get the Error in: "Microsoft Windows XP Professional Service Pack 3"

    And it runs ok in: "Microsoft Windows Server 2003 Enterprise Edition Service Pack 2"





    my error...
  • NOTE:

    Made and error on the machines.



    I get the Error in: "Microsoft Windows XP Professional Service Pack 3"

    And it runs ok in: "Microsoft Windows Server 2003 Enterprise Edition Service Pack 2"





    my error...

  • Hi Valentine,





    Try inserting a delay between TestExecute runs and let me know whether this helps:







    echo  Stay in Testexecute: RegressionTest

    :loop

    "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" "C:\TestComplete\TargitAppi\TARGITTestSuite.pjs" /r /p:TARGITRegressionTest /run /exit

    ping -n 20 127.0.0.1 > NUL

    GOTO loop
  • Hi David,



    Thanks for the reply.



    through some looking into and this link -->



    I have changed the code to:



    echo  Stay in Testexecute: RegressionTest

    :loop

    start /wait "TestExecute" "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" "C:\TestComplete\TargitAppi\TARGITTestSuite.pjs" /p:TARGITRegressionTest /run /exit /SilentMode

    GOTO loop





    ... It works now.
  • Hi David,



    I was too hasty in saying the error does not come again, because I had a 'silent mode' set, I did not notice the error.

    The error is still there despite the delay of ping -n 20 127.0.0.1 > NUL'.



  • Hi Valentine,





    How often does the problem occur? Can you stably reproduce this issue? Can you reproduce the issue with a single test execution without running it from the CMD window?
  • Hi David,



    I am currently running a test now and will get you more datails later.

    But what am sure of is:

    • when I start from the cmd scrit, TE starts. When I close the cmd window and use the right-click menu of TE to exit/close TE, then that error message comes up ( and the follow up of sending the error to you guys).



     


  • Hi Valentine,





    I would appreciate it if you submitted a request to us using the Contact Support form. I will send you steps to perform additional investigation of this problem that will help us find more information on it.
  • Hi David,

    have you got anymore information for me?...

    My code is still:



    REM Clears the screen

    CLS

    @ECHO OFF

    REM Launches TestExecute,

    REM executes the 'Auto Testing specified project

    REM and closes TestExecute when the run is over

    REM "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" "C:\TestComplete\TargitAppi\TARGITTestSuite.pjs" /r /p:TARGITRegressionTest /run /exit

    ECHO Infinite execution of TARGITRegressionTest Test

    ECHO Look for updates

    echo if found :

    echo  Run Test and close Testexecute

    echo else

    echo  Stay in Testexecute: RegressionTest

    :loop

    start /wait "TestExecute" "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" "C:\TestComplete\TargitAppi\TARGITTestSuite.pjs" /p:TARGITRegressionTest /run /exit

    ping -n 20 127.0.0.1 > NUL

    GOTO loop





    And still it works in windows server 2003 and not in windows XP, when I click on the taskbar icon of testexecute and choose 'stop' or 'Exit' I get the error message:


    • "TestExecute is in playing state. Do you want to exit?': I select Yesy and then the error appers



  • Hi Valentine,





    Thanks for information. I tried to reproduce the problem using your batch file and description with a sample project, but failed. It seems that the problem occurs only in conjunction to your tested application. Is it possible for you to send the application to us so we can try to recreate the problem here?





    Also, you mentioned that after the error occurs, TestExecute displays a crash dialog that suggests submitting a report to us. Could you please send the report when the issue occurs next time? Please specify your name and e-mail address when sending the report so I can find it.





    BTW, have you tried using TestExecute 8?