While working with our applications, we see our application's performance going
down on performing a particular action. Reasons for this might be different. We
mainly see these kind of issues when resources reach its capacity. Resources
can be CPU resources, memory, application, physical disk and network resources.
So, finding these kind of bottlenecks is difficult in manual testing. If you
are using QTP to automate your testing, then you have a solution for this.
Ref: http://goo.gl/FXePGx |
QTP provides a functionality called Local System Monitoring.
Enabling this functionality for a particular script lets QTP monitor and record
resource usage for each and every step performed. Finally, it shows a graph
with resource usage statistics. When a particular step is selected in result,
corresponding resource stats will be shown in graph. So that, it would be easy
to know on which action in application, performance is going down and the
reason for this (memory leak/thread leak/gdi object count, etc..). In addition,
you can export data from the System Monitoring tab for a variety of file types.
Following are few simple steps which need to be performed to
monitor system counters:
- Enable Local System Monitoring from File->Settings->Local System Monitor.
- Provide the name of the application to be monitored.
- Add system counters to be monitored. We can even set limit to system counters. So that whenever a particular counter reaches the limit, your test run will fail.
- Once test run completes, result page will shows system monitor graph.
These statistics can be exported to any type of file for
further investigation.
No comments:
Post a Comment