Forum Discussion
AlexKaras
14 years agoCommunity Hero
Hi Aneez,
Yes, the provided code is for TestComplete and in order to use it you must install HISUtils extension (File | Install Extension...) that is provided with TestComplete.
The difference between measurements done with TestComplete and AQTime profiler is that with TestComplete only you will be able to say: "Well, it takes 15 seconds to open form A. Obviously, this is too much, but I have no idea why it takes that long. Maybe developers can do something to speed things up".
With AQTime your speech might be like this: "I measured time it takes form A to open and it appeared to be 15 seconds. Then I profiled it with AQTime and it showed that function A requires 6 seconds, function B requires 4 seconds and function C requires 2 seconds. All other functions executed while opening form A consume 3 seconds in total and worth no attention now. Maybe developers can refactor functions A, B and C so that they consume not more than 5 seconds in total? This will give us the total time to open form A equal to 8 seconds which satisfies our requirements".
I.e. with TestComplete you can measure how long does it take to do some UI-related action, but can say nothing about internals of the action.
With profiler you can measure how much time is spent in this or that function/line of code.
Yes, the provided code is for TestComplete and in order to use it you must install HISUtils extension (File | Install Extension...) that is provided with TestComplete.
The difference between measurements done with TestComplete and AQTime profiler is that with TestComplete only you will be able to say: "Well, it takes 15 seconds to open form A. Obviously, this is too much, but I have no idea why it takes that long. Maybe developers can do something to speed things up".
With AQTime your speech might be like this: "I measured time it takes form A to open and it appeared to be 15 seconds. Then I profiled it with AQTime and it showed that function A requires 6 seconds, function B requires 4 seconds and function C requires 2 seconds. All other functions executed while opening form A consume 3 seconds in total and worth no attention now. Maybe developers can refactor functions A, B and C so that they consume not more than 5 seconds in total? This will give us the total time to open form A equal to 8 seconds which satisfies our requirements".
I.e. with TestComplete you can measure how long does it take to do some UI-related action, but can say nothing about internals of the action.
With profiler you can measure how much time is spent in this or that function/line of code.