Install
Our company recently started using InstallShield to create .exe installers instead of the traditional .msi install using windows installer tools; I recreated my Keyword Test to go through the steps in...
Forum Discussion
Hey AQA/ SmartBear Team,
Still cant figure this out. Robert has advised me but I am unsure about what his advise means, can someone please help out.
Here are our messages:
Robert -
Each step in your install, while it shares the same class, has a different caption. What I would do is actually map each step as a different object in NameMapping, each one utilizing the caption to distinguish. This will help mitigate some problems
later.
Secondly, you’re MSIEXEC name mapping is very non-specific. As mentioned elsewhere, there are multiple MSIEXEC processes launched, usually, so you’ll need to make sure that you create a distinction between the processes. Figure out which MSIEXEC process is the one you want and add the process index in.
Take care of these two things and try again. If nothing else, work with your name mapping for the MSIEXEC because what might be happening is that you’re automation is grabbing the wrong one and using the one that doesn’t actually have the window attached to it, hence the error you’re getting.
My response -
I am not sure how to do any of the things you have described. Are there articles on how to utililize the captions to distinguish between objects, and how to add a process index? When I go to Name Mapping for MSIEXEC I do not see a process index and for each button in the subtree under MSIEXEC i see the WndCaption field but do not understand what is wrong with these values.
Basically everything in Name Mapping looks "okay" to me, I do not know how to spot what is wrong with it.
I've also attached the project files if any of you want to take a look. The keyword test in question is "Install" - i did not include AERMOD.exe that is referenced in the TestedApps because the file size is 100+ MB.
Still cant figure this out. Robert has advised me but I am unsure about what his advise means, can someone please help out.
Here are our messages:
Robert -
Each step in your install, while it shares the same class, has a different caption. What I would do is actually map each step as a different object in NameMapping, each one utilizing the caption to distinguish. This will help mitigate some problems
later.
Secondly, you’re MSIEXEC name mapping is very non-specific. As mentioned elsewhere, there are multiple MSIEXEC processes launched, usually, so you’ll need to make sure that you create a distinction between the processes. Figure out which MSIEXEC process is the one you want and add the process index in.
Take care of these two things and try again. If nothing else, work with your name mapping for the MSIEXEC because what might be happening is that you’re automation is grabbing the wrong one and using the one that doesn’t actually have the window attached to it, hence the error you’re getting.
My response -
I am not sure how to do any of the things you have described. Are there articles on how to utililize the captions to distinguish between objects, and how to add a process index? When I go to Name Mapping for MSIEXEC I do not see a process index and for each button in the subtree under MSIEXEC i see the WndCaption field but do not understand what is wrong with these values.
Basically everything in Name Mapping looks "okay" to me, I do not know how to spot what is wrong with it.
I've also attached the project files if any of you want to take a look. The keyword test in question is "Install" - i did not include AERMOD.exe that is referenced in the TestedApps because the file size is 100+ MB.