Forum Discussion
TanyaYatskovska
12 years agoSmartBear Alumni (Retired)
Hi,
I've looked into your project. According to the Test Log, the Aliases.MSIEXEC object isn't found. Let me explain what is going on. First of all, the Aliases.MSIEXEC object is mapped OK. However, you are using the Required Children feature. Thus, in order to identify the displayed object by TestComplete, your Aliases.MSIEXEC object must contain the wndMsiDialogCloseClass and wndMsiDialogNoCloseClass child objects at a time. But, I don't see the wndMsiDialogNoCloseClass object in the screenshots in your test (maybe I'm wrong on this point). So, if TestComplete cannot find one of these windows, it doesn't recognize the displayed MsiExec process as the mapped object, and the test fails.
Besides that, as the installation process takes several steps, you will see different buttons, text, etc. on each step. In your test, you mapped the Aliases.MSIEXEC.wndMsiDialogCloseClass object by using all buttons that you can see when installing. As a result, TestComplete will never find this window. So, you either should map every single step as an individual window with its own buttons, or do not use buttons which are different for different steps as required children for the installation window.
If you choose to map each step as an individual window, you will need to handle the following steps:
Step #1:
Map this window by the text (you can use * to change the variable part in it) - Welcome to the InstallShield Wizard for Honeywell Video Analytics*
And add the control buttons to this mapped object by their caption (you can use the Visible and Enabled properties as well): Back, Next, Cancel
Step #2
Map this window by the text in the caption - License Agreement
The radio buttons can be mapped by their text as well: I accept the terms in the license agreement
Map the control buttons as you did on step #1.
And so on...
Related Content
- 14 years ago
Recent Discussions
- 3 hours ago