What action is happening in your test when the crash occurs? What type of application also?
Hi cunderw!
The crash occurs when these conditions are met:
- TestComplete clicks Load on a display load window
- TestComplete doesn't click Load and the test is stopped manually prior to this point. We then click Load.
- TestComplete doesn't click Load and the test is stopped manually prior to this point. We then click Cancel.
The application is written in Delphi code and is a desktop application. For anything more than that you'll have to be more specific ;)
Thanks
Jenny
Does your AUT have any kind of debug log you can parse? What type of object is 'Load' and how are you accessing it / clicking it.
Also what exactly are you doing prior to clicking Load.
I might be way off, but my guess is that you're accessing something in the application in an unexpected way and it might be throwing a null error or something similar. I've seen this in some of my AUTs.
Hi
Prior to clicking Load the test is updating details in the database and a configuration setting in a different application that is referenced by this application.
The Load button is a third party component from a provider called Raize. When that button is clicked data from the DB is loaded and other components in the Graphical are updated as a result.
We have reviewed logs to try and debug this already. Though, they have focused around the thread creation \ thread synchronization only.
In the keyword test the Load object is being clicked by an on screen action which is executing just fine but obviously the crash is occurring. When the crash happens TestComplete still has the mouse disabled and it's only when the application is ended through Task Manager does TestComplete become responsive and give us the log as normal.
I've been too busy to raise this issue with SmartBear Support but willing to do this if people think it will help.
Thanks,
Jenny
