> ## 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.

# Discover and Run Tests

> Use your AI assistant to explore what tests are available in Spur and run them without leaving your editor.

<iframe src="https://www.loom.com/embed/3096323fa3f94ff3bd8836248a2a781d" title="Spur MCP product walkthrough" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

## Who is this for?

If you've just joined a team using Spur — or you are taking a look at tests someone else wrote — you may not know what test coverage already exists. Rather than clicking through the Spur dashboard to find out, you can ask your AI assistant to tell you.

This workflow is especially useful when you:

* Are new to a codebase and want to understand what's already tested
* Need to run tests for a feature you're working on but aren't sure what's available
* Want to quickly check if a specific flow has coverage before writing new tests

## Walkthrough

<Steps>
  <Step title="Ask what tests exist">
    Start with a broad question like *"What tests do I have?"* or narrow it down: *"What tests do I have for Adding to Cart?"*

    Your agent calls `list_tests` to pull all tests in your active application, then filters by name and description to find relevant matches.
  </Step>

  <Step title="Choose the Tests">
    The agent returns a list of matching tests with their IDs, suites, URLs, and descriptions. You can ask follow-up questions like *"What does the checkout test cover?"* to get full step details via `list_tests` with the `test_id`.
  </Step>

  <Step title="Run tests directly">
    Once you've found the right test, tell your agent to run it: *"Run this on staging."*

    The agent calls `run_tests` with the correct environment name and configuration, then monitors the run status. The agent will prompt you to fill in any configurations that it is missing.
  </Step>

  <Step title="Review results">
    When the run completes, ask *"How did it go?"* The agent calls `get_test_run_overview` to summarize the results — passing steps, failures, and warnings — so you can decide what to do next.
  </Step>
</Steps>
