Forum Discussion

vatbub's avatar
vatbub
Contributor
8 years ago

Launching TestComplete takes ages

Hey, we have a ProjectSuite containing 3 Projects (iOS, Android, common). As the names indicate, we seperated the two os and common functions. However, the iOS and Android Projects contain reference...
  • tristaanogre's avatar
    tristaanogre
    8 years ago

    Ah, yes... that would take a long time to start.

    A suggestion to prevent this from happening again:

     

    1) Export your logs to a central location after every run. That way the logs are backed up and archived for future reference.  Do this because the next suggestion is to

    2) In your TestComplete options (something you'll need to set on all machines running the tests and within TestExecute instances as well),, under Engines -> Log, turn off the "Store all logs" option and select a meaningful value for "Number of recent logs to keep". TestComplete will automatically purge older logs to keep to that number. 

     

    Glad that you figured out the problem.  Hope my suggestions help preventing that in the future.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
8 years ago

By "Launch TestComplete", are you launching to execute the tests or simply launching to edit the project?

If the former, while it isn't "compiling code", it does need to load the script and test code into memory in order to be able to execute it. If you have a very large project with lots of units, lines of code, etc., this could take time. 

  • vatbub's avatar
    vatbub
    Contributor
    8 years ago

    Hi,

    sorry for not replying for so long.

    We finally fixed the issue. What I meant was the time to actually open the ProjectSuite. This delay was caused by the number of logs we had in it from our nightly tests. Now, we removed the logs from the ProjectSuite and TestComplete starts much quicker.

     

    Regards,

    vatbub

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      8 years ago

      Ah, yes... that would take a long time to start.

      A suggestion to prevent this from happening again:

       

      1) Export your logs to a central location after every run. That way the logs are backed up and archived for future reference.  Do this because the next suggestion is to

      2) In your TestComplete options (something you'll need to set on all machines running the tests and within TestExecute instances as well),, under Engines -> Log, turn off the "Store all logs" option and select a meaningful value for "Number of recent logs to keep". TestComplete will automatically purge older logs to keep to that number. 

       

      Glad that you figured out the problem.  Hope my suggestions help preventing that in the future.

      • vatbub's avatar
        vatbub
        Contributor
        8 years ago

        Hi Robert,

        yeah, we are currently implementing an export to our CI. However, we are still struggling with it but this has to do with our ci rather than with TestComplete.

         

        Anyway, thanks for the tip and have a nice weekend,

        vatbub