Next button recognition is not stable

OK,i solved that by using conditional mode for the msiexec.exe process.

is there another way do make sure it will work?

by the way is there index 0?

thanks

But, still i have the same problem with a button.

what is going on here???

Timing is most likely the issue.  If there are delays between clicking the next button on the previous screen and the next button on the next screen, the automation may be moving faster than the screens can keep up.  Try using a WaitChild or similar method before you select the Next button to put in a "smart" delay before going on.

Hi Robert,

did that.

basically i'm running full installation and then i want to upgrade by running the following.




function Installation1_0_1PatchUpgradeFrom1_0_0()

{

TestedApps["Patch_1_0_1"]["Run"]() 

//Clicks the 'btnUpdate' button.      

  Aliases["MSIEXEC"]["wndMsiDialogCloseClass"]["WaitAliasChild"]("btnUpdate",25000)

  Aliases["MSIEXEC"]["wndMsiDialogCloseClass"]["btnUpdate"]["ClickButton"]();

  //Clicks the 'btnFinish' button.      

  Aliases["MSIEXEC"]["wndMsiDialogCloseClass"]["WaitAliasChild"]("btnFinish",30000)

  Aliases["MSIEXEC"]["wndMsiDialogCloseClass"]["btnFinish"]["ClickButton"]();

  Log["Message"]("1.0.1 PATCH Install ended - Upgrade") 

}



it just doesn't recognize the btnUpdate. can't understand why

Is 25 seconds long enough?  Out of curiousity, increase the value from 25000 to something really "silly" like 120000 (that's a full 2 minutes) just to see what happens.

Unfathomably 120000 is not doing the job,that's weird because i did worked right after creating the recording and somehow it sopped working.

any other ideas?

When trying to record the button click again i'm getting the following line 

Aliases["msiexec1"]["wndMsiDialogCloseClass"]["btnUpdate"]["ClickButton"]();

while the original is

Aliases["MSIEXEC"]["wndMsiDialogCloseClass"]["btnUpdate"]["ClickButton"]();

why is that happen.that causing the TC not to recognize but why is it happening?

thanks

It sounds like you have multiple MSIEXEC processes running (which is normal) and so, when you get to that point in your automation, the update button is associated with a different process. 



What you might want to do is work with your NameMapping to uniquely identify your MSIEXC process based upon the child objects (using "Required Children") rather than index.  That way, no matter what the index is, so long as it has the appropriate child objects, it will always recognize the proper object.

Well, i think i did what you says.

i went to the NameMapping stand on the btnUpdate's parent pbject and from the right side under the Required Children i checked all check boxes(just in case).if what i did is correct it's still doesn't work. :(

You need to do that, not on wndMsiDialogCloseClass but on the Aliases.MSIEXEC object.