check toolbar button state

Check the state of a button on a toolbar against an expected state.
NameDescriptionTypeModifier
window

TA name of the window.

Interface EntityNone
toolbar

TA name of the toolbar control.

Interface ElementNone
button

Button, as identified by its caption or index value.

StringNone
expected

Expected state.

Allowable values:

  • -1 or disabled: Button is disabled.
  • 1 or enabled: Button is enabled but not pressed.
  • 2: Button is enabled and selected (on), or enabled and pressed.
  • pressed: Button is enabled and pressed.
  • checked: Button is enabled and selected (on).

Value Set-1, disabled, 1, enabled, 2, pressed, checked
Result is Passed if the values match, otherwise Failed.
This action may be used within the following project items: test modules and user-defined actions.
This action is applicable to the following controls: toolbar.
Example - Case 1: Using a text value for button

        
        	interface			
use interface	Music Library			
&nbsp				
	window	toolbar	button	expected
check toolbar button state	library	toolbar	Search	disabled
check toolbar button state	library	toolbar	Show/Hide	enabled
check toolbar button state	library	toolbar	About	pressed
        
    
Example - Case 2: Using a numerical index value for button

        
        	window	toolbar	button	expected
check toolbar button state	library	toolbar	2	-1
check toolbar button state	library	toolbar	4	1
        
    
  • button argument:
    • The button may be specified by either of two means: the caption text, or its numerical index (Indexes are one-based. That is, numbering begins at 1).
    • 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.
  • 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