Forum Discussion

mustafayol's avatar
mustafayol
Contributor
4 years ago

Test Execute | Cannot Launch another instance of this application

1) I installed test complete and test execute on my computer. 2) I created a sample project on a network location 3) I run the specific test routine via test executed --> All good till now. When I...
Marsha_R's avatar
Marsha_R
Moderator

TestExecute is trying to run your copy of TestComplete, so no, you can't be in both on the same machine at once.  

mustafayol's avatar
mustafayol
Contributor
4 years ago

Let's say there are no instances of Test complete and test executor. I started a test by using test executor from the command prompt.

 

"C:\Program Files (x86)\SmartBear\TestExecute 11\Bin\TestExecute.exe" "D:\TestComplete\TCPJS_OT_6_0\TCPJS_OT_6_0.pjs" /r /p:Prj_Admin /u:Entry /routine:test12

 

After the test is finished, if I run another command like above, I am getting the error "Cannot Launch another instance of this application". Not to get the error, I have to exit from the icon in the bottom tray (kill app basically).

My question, should I kill the test executor after I run the test? Then I will be able to run a new test again with the executor. I can add another bash script, then kill the test executor. But this is not a good approach, I wonder if the test executor has the capability to kill itself after it finishes its task.

  • Marsha_R's avatar
    Marsha_R
    Moderator
    4 years ago

    TestExecute does know how to shut down when the test is complete. 

     

    I would start looking for reasons that the test isn't actually done when you think it is.  Is it a really long test?  I have seen long tests that end up with a huge log and it can take a minute or two to finish writing the log and the test isn't over until that is done.  Try running the test and then waiting an extra long time, maybe 5 minutes and then look in Task Manager and see if TestExecute or TestComplete is still there.  If not, then try the second run and see if you still get the error message.

    • mustafayol's avatar
      mustafayol
      Contributor
      4 years ago

      Hello guys, I will try your suggestions as soon as I have time.

      Many thanks for your support at the moment.

      greetings,

      Mustafa

      • mustafayol's avatar
        mustafayol
        Contributor
        4 years ago

        Ok, finally  I had the chance to try, here is the scenario.

         

        1) On my computer only test executor is installed. I also added its bin directory to the path under environmental variables of the computer.

        2) I created a simple test, only logging out the message as "Test is done", that is not a long test. One unit and under the unit, there is only one routine -> testRoutine1

        3) I run the test via test executor, test is OK, I can see the results.

         

        At this point, if I try to run the same test again with same testexecutor command, I got the error  " Cannot Launch another instance of this application"

         

        4) When I check the windows tray at the bottom left I see the small test executor icon, meaning, the error is right and test executor did not close itself after I run my test.

        See the picture, please.

         

         

        5) If I want to run my test again, I have to go to tray, left click and exit test executor. 

        ı assume I miss a point, that helps the executor to stop its own process / task, Then if I want to run another test, I should not get the error "Cannot Launch another instance of this application"