does tree node exist

Return a Boolean value to indicate whether a specified tree node exists.
NameDescriptionTypeModifier
window

TA name of the window.

Interface EntityNone
tree

TA name of the tree control.

Interface ElementNone
node path

Path to the node (see ).

StringNone
variable

(Optional) Variable to receive the returned Boolean value.

Possible returned values:

  • 1: Node found.
  • 0: Node not found.

StringNone
A Boolean value to indicate whether a specified tree node exists.
This action may be used within the following project items: test modules and user-defined actions.
This action is applicable to the following controls: tree view, tree table, tree list.
Example - Case 1: Using a text value for node path

        
interface
use interfaceCar Rental
 
windowtreenode pathvariable
does tree node existview carscar select treeCar Types/Standardboolean1
does tree node existview carscar select treeCar Types/SUVboolean2
Example - Case 2: Using a numerical index for node path

        
windowtreenode pathvariable
does tree node existview carscar select tree1/4boolean
  • node path argument:
    • The node path may be specified by its display textor by a numerical index representing its cardinal placement in its branch, with index values starting at 1.
    • If a node path of more than one item must be specified, use forward slashes ( / ) as delimiters between node levels.
    • Enclose a numerical text string in quotation marks to differentiate it from a numerical index value. For example, if a text value of an item in a control has a value of 12, you should reference that item by passing 12 surrounded by quotation marks (that is, "12") instead of the numerical 12. Passing the numerical 12 is treated as a reference to an item with an index of 12, rather than an item holding a text string value of 12.
  • variable argument:
    • If the variable in argument variable has not been declared, the action creates it as a global.
    • If the variable argument is left empty, TestArchitect supplies a global variable with the name _result.
  • This action supports the <ignore> modifier. If the string <ignore> is present as the value of any of the arguments, or any argument contains an expression that evaluates to <ignore>, the action is skipped during execution.

Copyright © 2025 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1 (650) 572-1400