Contributions
- 2KViews0likes2Comments
- 2KViews0likes6Comments
Re: Test Complete: Switch to a different application
Marsha_Rwrote: 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()2KViews0likes0CommentsRe: Test Complete: Switch to a different application
cunderwwrote: 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 there2.1KViews0likes10CommentsRe: Convert the saved xml report to a Junit report
We have a strange way of starting the job - lots of prerequisites before, but let's say we can bypass that. The most annoying thing is that there is nowhere in the report, that TestComplete provides, the build or version of the application you are executing your tests on. In order to manage that, we are modifying the report and insert the version number of the application as a tree node in the final report.2.1KViews0likes2Comments