How do I keep track of unexpected UI bugs during GUI Automation Load Tests?
|GUI Test Automation – How-To Tips!|
While conducting GUI Automation Load Tests is a must in order to identify any unexpected UI bugs and crashes under varying loads, keeping track of such issues is far from easy. The inherent nature of load tests (high traffic and quick execution speed) makes it a daunting task to capture GUI bugs. Therefore, it’s recommended to log all UI failures (Error Windows, Warning Pop-ups, Crash Dialogs, Exceptions stack traces, Windows fatal error dialogues) to an external log file. Further, it’s a good practice to log the loading time to identify any potential performance or UI resource crunch issues.
The external log file must be used for reconciliation while replaying the recording of your application’s automated GUI test cases.