Challenges with TestComplete Record and Playback for Enterprise Desktop Application

Hi Ramal,

It's hard to say exactly what's going wrong however, the fact that you can re-record and that works is a clue.  That would tend to lead me to believe the object identification properties aren't ideal.  More specifically, they may be using a property that isn't static.

Normally the error in the log is more helpful when that is the case.  Nevertheless, I would start with checking the name mapping properties for your objects and make sure they are using properties that you are confident won't change from run to run.  Some object IDs and other properties in applications can be created at runtime.  The name mappings much be configured to accommodate that case.

For instance, in our desktop application each window has a WndClass.  However, that class can change.  I use that property in the name mappings with a wildcard because I know the first part is always the same (e.g. "Afx:00*").  In combination with the WndCaption I have unique identification properties.  In the below case I've wildcarded two of the identification properties that I know can change.

Name mappings are created automatically during recording.  Unfortunately, they aren't always created with reliable properties.  I always go back and fine tune them.

Getting the hang of name mapping takes a little while.  Once you figure it out you can make your test more robust and performant.  If you haven't read the help topic check it out here:
Name Mapping | TestComplete Documentation

Good luck, John