Forum Discussion

SilviaG's avatar
SilviaG
New Contributor
9 years ago

Are my application execution times inflated because of Test Complete execution delays?

I am trying to test my application performance during test execution.

I use keyword testing with the Aqperformance or the Start counter object. It seems to me that the time that I get from these measurements is considerably higher than the time I measure manually. 

Are there any considerations to make these measurements more accurate?

 

I am trying to measure the time it takes to open the first page in my application. I have the following actions:

 

aqPerformance Start Variables.vOpeningFirstPage, ... 


BidRecordRow DblClick 


DrawingCanvas WaitProperty .imageContainer.drawingCanvas.Exists, true, .


While Loop (ImageContainer.drawingCanvas.Enabled Equals false) OR (ImageContainer.drawingCanvas.Visible Equals false)
While Loop (NavToolbar.nextPageButton.Enabled Equals false) OR (NavToolbar.nextPageButton.Visible Equals false)


aqPerformance Value [Get] Variables.vOpeningFirstPage 

 

3 Replies

  • Ravik's avatar
    Ravik
    Super Contributor

    We can add start and end time to get the page load but  TC is not actual performance testing tool so we can't say that time is absolutely correct.

     

    Can you please check with "Performance Counter" feature in TC, it may help you.

     

    Tools -> Current Project Properties -> Performance Counter -> Add -> Enter your IP -> select you desire test type

     

    • Colin_McCrae's avatar
      Colin_McCrae
      Community Hero

      Well, you're doing this on a desktop application and effectively using a stopwatch.

       

      But for the stopwatch to stop, you are checking various object property states to determine when something is complete. And to do this, TestComplete has to check the updated state of object(s) each time you loop. Which can indeed cause delays as it refreshes the object map.

       

      So your times are likely to be artificially high. I would hope not by much, but I imagine if your application is a very busy object model, it could increase the times by more than you'd like as the refresh rate will probably slow down, the more objects it's having to deal with.

       

      How much higher are the reported times vs what you would expect?

  • SilviaG's avatar
    SilviaG
    New Contributor

    Thanks for your replies... I changed the loops for WaitProperties and my time now is much more approximate to the actual times.