You say "to identify the "msiexec" process, are more or less the same since the beginning." Which leads me to believe maybe something there is changing? In your object tree I also see more than one msiexec object. What does your mapping look like for that?
Also, where exactly is it failing? And what is the error message for the failure?
Thanks for your reply, cunderw.
I recreated the tests for the installer. So the properties of the msiexec process are the same since then. The second msiexec process somehow belongs to the first one. Don't ask me how, but it starts when I execute my installer. And there is no mapping for it, since all I need is on the msiexec process which is shown collapsed in the object tree screenshot.
If something is changing during rebuilding of the installer, I don't the it in TestComplete. Because I can highlight everything with TestComplete on the new builded installer, to me the mapping seems to be okay.
TestComplete is telling me that it cannot find the Aliases.msiexec.wndMsiDialogCloseClass.btnWeiter.
Do you need any other screenshots to find the cause?
Fred
If you can highlight the objects after run time, but they are only not found while running your test, then as tristaanogre mentioned it's probably a timing thing and you will need to include one of the wait methods for your objects to exist and be visible.
Hey Carson,
sorry for the late response.
So by putting delays in between you mean the dealy like I used in the installer seen in my post above?
Or is there a delay option where TestComplete tries to find an object within a timespan of e.g. 15 seconds?
Thanks,
Fred
So I've added a lot 10 second delays before almost every action on my installer and the application, which gets installed. Still, I get the error...
What else could I do?
Any hints are much appreciated!
Fred
Here's my other thinking on this:
It may be that we're doing EVERYTHING right in mapping, delays, etc... but the simple fact is that there are more than one msiexec processes running when you run your tests. So, when it gets to that point, the mapping may be pointing to the msiexec process that is not the one with the UI displayed and so the object is coming up not found.
There have been multiple threads here on the forums of people who are trying to automate, through TestComplete, the use of the installer to install their application and, IIRC, this has been a standard problem they've experienced.
This may be one of those situations where doing an automated test may be more trouble than actually worth. However, one more suggestion... in your mapping for the process, have you tried adding "Required Children"? IIRC, only one msiexec process has the child objects of the UI. If you edit the process to indicate that it has certain required children, that MIGHT help out.
