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

# Vibe test

> Come up with a test plan for your vibe coding

> Automated browser testing after new vibe-coded changes/features.

Kyoto explores the code changes to see what frontend features were added or changed
then runs a series of tests to check if they work.

```sh theme={null}
kyoto vibe test
```

This command will review all uncommited changes for tests to run.

or, let coding agents vibe test themselves

<Note>Set up the [Kyoto MCP](/pages/integrations/mcp)</Note>

## Options

#### Scope

Change the scope that Kyoto will evaluate.

```sh theme={null}
# Default
kyoto vibe test                    # all uncommited changes

kyoto vibe test --last             # since last vibe test
kyoto vibe test -1                 # last commit
kyoto vibe test -3                 # last 3 commits
kyoto vibe test --since main       # branch changes
kyoto vibe test --staged           # staged changes only
kyoto vibe test --commit <sha>     # specific commit
kyoto vibe test --changes "file.ts:1-10,other.ts:20-30"  # specific files and lines
```

#### Modes

Run browser in headless mode

```sh theme={null}
kyoto vibe test --headless
```

Enable interactive mode to choose which tests to run

```sh theme={null}
kyoto vibe test --interactive
```

Watch for file changes and automatically run tests

```sh theme={null}
kyoto vibe test --watch
```

#### Instructions

```sh theme={null}
kyoto vibe test --instructions "test login flow"  # custom testing instructions
kyoto vibe test --timeout 5        # timeout in minutes (default: 1)
```