does context menu item exist

Return a Boolean value to indicate whether a specified item on a context menu exists.
NameDescriptionTypeModifier
window

TA name of the window.

Interface EntityNone
control

TA name of the control holding the context menu.

Interface ElementNone
item

Menu item or menu item path (see ).

StringNone
variable

(Optional) Variable to receive the returned Boolean value.

Possible returned values:

  • 1: Item found.
  • 0: Item not found.

StringNone
x

(Optional) Horizontal position of effective click on menu control, specified as distance in pixels from left edge of the control.

Default Value: horizontal center of the control.
StringNone
y

(Optional) Vertical position of effective click on menu control, specified as distance in pixels from top edge of the control.

Default Value: vertical center of the control.
StringNone
A Boolean value to indicate whether a specified item on a context menu 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: button, check box, checklist, clock, combo box, datetime, frame, label, list box, list view, menu, password, picture box, progress bar, radio button, rating bar, richtext, scroll bar, separator, spin, status bar, tab control, table, text box, toggle button, toolbar, trackbar, tree view, window.
Example - Case 1: Use text value

        
        	interface			
use interface	Music Library			
&nbsp				
	window	control	item	variable
does context menu item exist	search	songs list	Show artist	result
        
    
Example - Case 2: Use numerical index value

        
        	window	control	item	variable
does context menu item exist	search	songs list	5	result
        
    
  • item argument:
    • The menu item may be specified by its caption property or numerical index representing its cardinal placement in the menu, with index values starting at 1.

      Restriction: 
      Using numerical index values is not supported for Oracle Forms and Microsoft UI Automation (UIA).

    • If a menu path of more than one item must be specified, use arrow symbols ( -> ) as delimiters between menu items. For example, Vehicles->Cars->Four-door sedans.
    • 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.
    • In order for TestArchitect to access the items of a context menu, it must activate the menu by simulating a mouse click on the host control. In some cases, the default click location at the center of the control will not bring up the menu. Hence it is sometimes necessary to supply the click location via the x and y arguments.
  • 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 © 2024 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