Example - Case 1: The window and control arguments are specified

        
          	picture	window	control
click picture	/login button	login	login
&nbsp			
	window		
check window exists	welcome		
        
    

Result

Effect

Example - Case 2: The rect argument is specified

        
          	picture	window	control	rect	index	x	y	click type
click picture	/login button	login	login	1,1,100,100		0	0	left
&nbsp								
	window							
check window exists	welcome							
        
    

Result

Effect

• Built-in UI actions applied to iOS devices specify screen coordinates in points rather than pixels (For further details, refer to the built-in action get screen resolution).
• As a convenience when editing, you may drag the appropriate picture check node from the Picture Checks folder (in the TestArchitect explorer tree) into this action's picture argument.
• By default this built-in action applies a pixel-by-pixel image comparison technique. To switch to a keypoint detection image comparison, refer to picture algorithm and Key Points Modification tool for details.
• Note that if the referenced picture check holds multiple baseline images, each one is tested against the AUT bitmap until (and if) a match is found. Only a single "hit" is required for a match to be considered found.
• This action is applied to that part of the captured bitmap identified as the active area, with the remainder of the image ignored. The active area is determined by the combination of the window, control and rect arguments.
  To begin with, window and control determine the active UI element, which can be a control, window, or the full screen, as follows:

  window argument	control argument	active UI element is…
  omitted	omitted	entire screen (i.e., entire captured test image)
  specified	omitted	entire application window
  specified	specified	specified control

  With the active UI element established, the rect argument then (optionally) specifies a rectangular active area relative to the active UI element (If no rect argument is specified, the active UI element itself is the active area).
• rect argument:
  • The above figure illustrates the active area that applies when both the window and control arguments have been specified (establishing a picture control as the active UI element), and the values for rect are such that it covers both a portion of the active UI element as well as an area outside of it. In such a case, the active area is the area of overlap between the UI element and the rect area.
    Any of the four sub-arguments of rect may be omitted, but all values must maintain their comma-delimited places to ensure correct assignment (For example, setting rect to  , , 100, 50 specifies an active area of width=100, height=50, whose top-left corner coincides with that of the active UI element).
  • In most cases, the rect area, if specified, defines a sectional area whose borders reside within the active UI element, so that the rect area itself is the active area. But that is not necessarily the case. The following three images illustrate the general case for how the active area is determined when the rect area is specified.
    
    The general rule for determining the active area is as follows:
    

    rect area:	resulting active area:
    not specified	the active UI element
    overlaps the active UI element	the intersection space (Cases 1 & 2 above)
    no overlap with active UI element	the active UI element (Case 3 above)

• If the action fails to find the specified instance of the target image, an error is generated.
• 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.