> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spurtest.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Click

> Simulate click interactions on elements across your application.

## Overview

The click action triggers an interaction when the agent presses on a specific element. Spur supports standard left clicks, double clicks, and right clicks.

## Click Types

<Columns cols={3}>
  <Card icon="arrow-pointer" title="Single Click">
    Standard left click for buttons, links, checkboxes, and other interactive elements.
  </Card>

  <Card icon="computer-mouse" title="Double Click">
    Double left click for selecting text, opening items, or triggering edit modes.
  </Card>

  <Card icon="bars" title="Right Click">
    Right click to open context menus or access additional options on an element.
  </Card>
</Columns>

## Common Use Cases

<Frame caption="Form submission">
  <img src="https://mintcdn.com/spur/9IFtS_isfyhWoPyj/images/Click/click_ex_1.png?fit=max&auto=format&n=9IFtS_isfyhWoPyj&q=85&s=7380d971a77572fe99f119e95996b757" alt="" width="1046" height="126" data-path="images/Click/click_ex_1.png" />
</Frame>

<Frame caption="Navigation">
  <img src="https://mintcdn.com/spur/9IFtS_isfyhWoPyj/images/Click/click_ex_2.png?fit=max&auto=format&n=9IFtS_isfyhWoPyj&q=85&s=9129a8a901d8201c6b79a805056d71b6" alt="" width="1040" height="128" data-path="images/Click/click_ex_2.png" />
</Frame>

<Frame caption="Modal interactions">
  <img src="https://mintcdn.com/spur/9IFtS_isfyhWoPyj/images/Click/click_ex_3.png?fit=max&auto=format&n=9IFtS_isfyhWoPyj&q=85&s=4eb5bc115c3d746b502962bbb1dc295b" alt="" width="1044" height="116" data-path="images/Click/click_ex_3.png" />
</Frame>

<Frame caption="Table operations">
  <img src="https://mintcdn.com/spur/9IFtS_isfyhWoPyj/images/Click/click_ex_4.png?fit=max&auto=format&n=9IFtS_isfyhWoPyj&q=85&s=c11740f3dfecf51083ce91af105a235f" alt="" width="1050" height="126" data-path="images/Click/click_ex_4.png" />
</Frame>

## Best Practices

* Be specific in your element descriptions so the agent can reliably identify the correct target
* Include surrounding context when targeting dynamic elements
* Consider using a [Wait](/authoring-tests/test-side-peek/step-types/actions/wait) action before clicking on content that loads dynamically
* Verify the click result when the interaction is critical to the test flow

<Warning>
  Avoid generic descriptions like "Click the button". Always provide enough context for the agent to identify the correct element.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Element Not Found" icon="magnifying-glass">
    If the agent cannot find the element:

    * Check if the element is visible in the viewport
    * Ensure the description matches what is displayed on screen
    * Add more context such as nearby text or section names
    * Use a Wait action if the element loads dynamically
  </Accordion>

  <Accordion title="Wrong Element Clicked" icon="triangle-exclamation">
    If the agent clicks the wrong element:

    * Add more specific context to distinguish the target
    * Include nearby text or landmarks
    * Specify the element type explicitly (e.g. "Click the Submit button" instead of "Click Submit")
  </Accordion>
</AccordionGroup>
