Forum Discussion

BrandonH's avatar
BrandonH
Contributor
7 years ago
Solved

Checking the success of a clickButton action

Hi,        I'd like to test whether a series of button clicks was successful (i.e. were all the objects found and successfully clicked).  I first attempted this by putting them in a try/catch state...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    try/catch only catches code exceptions.  Object not found errors are not trapped by code try/catch logic.

     

    To that end, I would use, for each button, a "WaitAliasChild" call to detect if the button exists.  Then, if it exists, call the ClickButton action on it.  After the ClickButton is executed, do another check of some sort to detect if the results of the button click worked.  Something like this:

    function testMyButton(){
    var myButton;
    myButton = Aliases.myApp.MyForm.WaitAliasChild('MyButton', 10000);
    if (myButton.Exists) {
        myButton.ClickButton();
        if (newTextField.Text != 'It Works') {
             Log.Error('MyButton click button failed');
        }
    }
    else {
        Log.Error('MyButton does not exist');
    }
}
tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

try/catch only catches code exceptions.  Object not found errors are not trapped by code try/catch logic.

 

To that end, I would use, for each button, a "WaitAliasChild" call to detect if the button exists.  Then, if it exists, call the ClickButton action on it.  After the ClickButton is executed, do another check of some sort to detect if the results of the button click worked.  Something like this:

function testMyButton(){
    var myButton;
    myButton = Aliases.myApp.MyForm.WaitAliasChild('MyButton', 10000);
    if (myButton.Exists) {
        myButton.ClickButton();
        if (newTextField.Text != 'It Works') {
             Log.Error('MyButton click button failed');
        }
    }
    else {
        Log.Error('MyButton does not exist');
    }
}
  • BrandonH's avatar
    BrandonH
    Contributor
    7 years ago

    Thanks tristaanogre.  That's essentially how I do it now, although for some tests there is no identifiable way, on our UI, to determine that a ClickButton was successful. Is there a way to reference the log to check status?

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago

      Not really.  Is there some other effect like a data record in an SQL database, a field or option on a different screen, etc?  Generally, if there is no error on "ClickButton" than, generally, it can be assumed to be successful...

       

      ...kinda begs the question that if you have a button to click and no discernable difference in the application, why have the button? ;)  That's a humorous way of saying that there is some effect of the button somewhere in your application... If you were manually testing it, how would you verify it's success?  Whatever you would do manually, see if there is a way to do the same validation via your automation.

      • BrandonH's avatar
        BrandonH
        Contributor
        7 years ago

        I see your point.  The affect can be seen in the database (unfortunately TestComplete does not have access to it), however, perhaps I can get creative and come up with something.  Thanks for your help