Quality Center and QTP Weirdness
I’ve often seen weird QTP behavior on my lab machines when I run long test sets from QC. This can be frustrating when you schedule normally-reliable tests at night, only to arrive the next morning to find that most of the later tests have failed.
These failures are usually unexplainable. Worse — the problematic tests always end up passing when they’re rerun.
Another issue I’ve observed is that the CPU on the lab machine shoots up due to the QTPro.exe sucking up all the memory.
Usually, a reboot resolves all these issues; however, it doesn’t help if you need to run long test sets from Quality Center.
Possible QTP ALM workaround
While mucking around with the QTP Remote Agent settings recently, I noticed a Cleanup option called “Restart testing tool after x runs.” (Everyone else may have already been aware of its existence, but it was news to me!) Anyway, this setting allows you to force QuickTest Pro to restart after x number of runs. So if you have a large test set that contains, say, 30 tests, you can test QTP restart after ten test runs.
How to change QTP Remote Agent settings
- Navigate to Start>Programs>HP QuickTest Professional>Tools>Remote Agent
- Right click on the QTP Remote Agent in the system tray and click on settings
- Under the Cleanup section change the ‘Restart testing tools after” run setting
Does it work to help long running test?
I’ve not yet tried it myself yet, but I’m hoping that using this setting will solve some of the funky QC issues I’ve seen. We’ll see. I’ll let you know if I find any interesting results.
Does anyone else use this setting, and does it work well for you? Let me know!