Forum Discussion

Contributor

10 years ago

"If Object Exists" is still running child opeations when object DOES NOT exits

I’m checking to see if our application was left in an open state before running the entire project suite. The test app, 95% of the time, would be left open in one of three main forms: login screen, t...

Ryan_Moran
10 years ago

You can use the If Object wizard under Test Actions for your keyword test. It should then have the Visible property available to select from on the Select Condition page of the wizard. If you're not using keyword tests then your script should be like so:

//JScript
function main() {
if (Aliases.PixelPointPOS.wndSystemObject.FormShape_InnerPanel.Panel.PixelButton.Visible == true){
//dostuff
}
}

//Make sure you spell it VISIBLE :)

martin_facchini

Contributor

you are right. :-D the object(s) Exist, but are not set to Visable.

Therfore, how would you use If Object to check against a property? The Test Action itself does not allow you to drill down to the ojebect's properties.

I've tried the follwing in the command line, but If Object does not understand what I'm trying to do:

Aliases.PixelPointPOS.wndSystemObject.FormShape_InnerPanel.Panel.PixelButton.Visable

Aliases.PixelPointPOS.wndSystemObject.FormShape_InnerPanel.Panel.PixelButton.Visable=true

Ryan_Moran

Valued Contributor

10 years ago

You can use the If Object wizard under Test Actions for your keyword test. It should then have the Visible property available to select from on the Select Condition page of the wizard. If you're not using keyword tests then your script should be like so:

//JScript

function main() {
if (Aliases.PixelPointPOS.wndSystemObject.FormShape_InnerPanel.Panel.PixelButton.Visible == true){
//dostuff
}
}

//Make sure you spell it VISIBLE :)

martin_facchini
Contributor
10 years ago
Thank you for your help. I understand the concept, and I understand and know how to drill down to various properties with the Property Checkpoint, but just to let you know that my coding skills are limited. :smileyfrustrated: :smileylol:

I therefore revised my keyword tests, but I’m still getting the same results, that is, the test continuers with the child operations, even though the IF…Then statement is not being met.

I’ve tried two variations of as per your suggestion:

Variation #1. Created a Property Check to check for the Visible property of the object I want, then used an If... Then statement set for last operation = True. This failed, and continued onto the child operation when the last operation came back False

Variation #2 I got rid of the property check all together and configured the If…then statement to check the object’s property (Visible) directly, with the same result.

In both variations, if the objects (my three different form scenario) are present, then the scripts work correctly and run when they should. It’s just when the object.visable are not visible that the script still tries to run the script.
- martin_facchini
  Contributor
  10 years ago
  hi, Ryan. I had to play with the child indents and finally got it to work.
  
  I had to unindent the first Else Statement so that I does not become a child (this dosen't make sense), but this worked. So, I tried un-childing the second Else as well, and it didn't work. :/ I finally re-childed the second Else under the first one, and now the second one works as well. (go figure) (see below)
  
  Thanks again for your help. Awesome!
  - Ryan_Moran
    Valued Contributor
    10 years ago
    I do see in your second screenshot that the condition appears to have the "Run Keyword Test" under the "If...Then" statement now.
    Glad you got it working ;).