My guess is that your second application is launched with some kind of dynamic identifier that Test Complete used to auto name map it. What does your name mapping look like compared to what you see in the object browser?
cunderw wrote:
My guess is that your second application is launched with some kind of dynamic identifier that Test Complete used to auto name map it. What does your name mapping look like compared to what you see in the object browser?
So they look the same :) that's the strangest part. Also if I do a recording of the actions, all actions get identified correctly, but when I play it again, it doesn't run. It waits for the app2 window to appear in order to press the import button, but doesn't find it - and I can see it's there
There has to be something different then that is changing betwen your recording and the playback. The auto generate name mapping is a great start, but will never be 100% complete so to speak. Can you provide screen shots of the object it can't find in the object browser, and then the properties being used in the name mapping? I would bet money there is something different.
here you are
Champion Level 3Let's see the name mapping for where you are in App 1 when you want to go to App 2 and also what you want to click in App 2.
Marsha_R wrote:
Let's see the name mapping for where you are in App 1 when you want to go to App 2 and also what you want to click in App 2.
Last action from app1:
Aliases.app1.fmDBman.InhaltPanel.ObjectList.TOutlookGroupedList.Drag(5, objectYpos, dbPoint.X, dbPoint.Y-100)
Then I am waiting for the app2 window to show up
Aliases.app2.WaitAliasChild("fmImportTSX", 180000)
and then clicking on import button
Delay(1000)
Aliases.app2.fmImportTSX.bnImport.ClickButton()
