Forum Discussion
HKosova
Alumni
14 years agoHi Aneez,
Profiling tools such as AQtime trace the application execution down to individual function calls and lines of code. So, they can show developers:
* which function calls and lines take most time to get executed and need performance optimization (performance profiling);
* on which lines memory is allocated that is not released, thus causing a memory leak (memory leak profiling);
* which functions and source code lines aren't executed during the application run (coverage profiling);
* and so on.
Usually, profilers are used by the developers during the application debugging, rather than by quality assurance engineers. However, it's a good idea to have profiling integrated with automated testing to better track performance, memory and coverage regressions.
For an example of TestComplete and AQtime integration, check out this video:
Using AQtime Coverage Analysis in Automated Tests
It shows how to perform automated testing with coverage analysis of the application's source code.
Profiling tools such as AQtime trace the application execution down to individual function calls and lines of code. So, they can show developers:
* which function calls and lines take most time to get executed and need performance optimization (performance profiling);
* on which lines memory is allocated that is not released, thus causing a memory leak (memory leak profiling);
* which functions and source code lines aren't executed during the application run (coverage profiling);
* and so on.
Usually, profilers are used by the developers during the application debugging, rather than by quality assurance engineers. However, it's a good idea to have profiling integrated with automated testing to better track performance, memory and coverage regressions.
For an example of TestComplete and AQtime integration, check out this video:
Using AQtime Coverage Analysis in Automated Tests
It shows how to perform automated testing with coverage analysis of the application's source code.