Automated test demo for Cline

Automated test demo for Cline

tailtest fires every time Cline edits a file. See it run.

tailtest for Cline v1.0.0 · 162 tests · MIT

Trigger model

.clinerules instruction + auto-approve OR /tailtest-test slash

IDE coverage

9+ editors

VS Code · Cursor · JetBrains IDEs · Antigravity · Zed · Neovim · VSCodium · Windsurf · Cline CLI

Best for

Anyone whose editor is not Claude Code, Cursor, or Codex CLI directly. One plugin reaches 8+ editors. Pairs with Cline's Plan / Act mode for explicit human review gates.

How tailtest fires in Cline

Cline plugin. MCP-driven; reaches 8+ editors via Cline's host coverage (VS Code, Cursor, JetBrains, Antigravity, Zed, Neovim, VSCodium, Windsurf, plus the Cline CLI).

Cline session
> Add discount validator to checkout.py
# .clinerules instruction + auto-approve OR /tailtest-test slash fires
tailtest: checkout.py queued
Generating scenarios... 8 written
pytest -q tests/test_checkout.py
8 passed 0.3s
tailtest: 8 scenarios -- all passed.
# Cline keeps building.

Install in Cline

Cline MCP Marketplace

Open Cline's Extensions panel inside your IDE. Search for tailtest. Click install. Cline clones the repo, installs deps, registers the server in cline_mcp_settings.json automatically.

Reload your conversation. Then run: 'set up tailtest in this project'.

Why pick the Cline variant

Anyone whose editor is not Claude Code, Cursor, or Codex CLI directly. One plugin reaches 8+ editors. Pairs with Cline's Plan / Act mode for explicit human review gates.

Or try another variant

Claude Code demo

PostToolUse hook

Cursor demo

afterFileEdit + stop hooks

Codex CLI demo

Stop hook + session_start

Read the Cline docs Compare all variants GitHub repo