Cline Testing.
One MCP plugin, 8+ editors.
Cline runs across VS Code, Cursor, JetBrains IDEs, Antigravity, Zed, Neovim, VSCodium, Windsurf, and the Cline CLI. Install tailtest-cline once via MCP and the test cycle works in all of them. Structured tool calls (R12 returns failure arrays), .clinerules rule pack, Memory Bank integration for cross-session context.
Install via Cline's MCP install dialog
Open Cline's Extensions panel in your IDE (VS Code, JetBrains, etc.). Search for tailtest or paste the GitHub URL into the MCP server install dialog:
# Cline clones the repo, installs deps, registers the server in cline_mcp_settings.json.
After install: reload your Cline conversation and run set up tailtest in this project. The MCP server writes a .clinerules/ directory with the rule pack and a Memory Bank entry for cross-session context.
How tailtest works with Cline (different from the others)
Cline shipped real hooks in v3.36 (May 2026). tailtest-cline's current v1.0.1 release predates that and uses .clinerules instructions + Cline's auto-approve feature for hands-off test cycling. Combined with the MCP server's structured tools, the result is comparable to hook-based plugins on the other hosts.
The .clinerules rule pack tells the agent to fire the test cycle after every file edit. Auto-approve handles the test execution permission so it doesn't interrupt the flow. The MCP server provides structured tools: scenario_plan, classify_failures, pick_template, setup, and ping.
A V14.10 migration to Cline's native PostToolUse hook is on the tailtest roadmap. That will give the cline variant the same deterministic per-edit firing as Claude Code + Codex. Today's instruction-based approach works reliably; the hook migration is an upgrade, not a fix.
Editor coverage (one install, many IDEs)
Cline's host coverage means installing tailtest-cline once lights up the test cycle in every editor Cline runs in:
What you get
MCP-driven structured I/O
R12 classification returns structured arrays, not free-text. Agent gets clean data to act on.
Memory Bank integration
Cross-session context. Recurring failure patterns recall on session resume. Per-file complexity scores persist.
Plan/Act mode native
SCENARIO PLAN gets reviewed in Cline's Plan mode before tests are written. UX-native enforcement.
162 plugin tests
tailtest-cline's own dogfood suite plus 12 slash workflows + tailtest-mode.
Common questions
Do I need to enable auto-approve in Cline?
Recommended. Auto-approve lets tailtest fire the test cycle without interrupting your flow. Default approval prompts mean you'd click through every test execution.
Where do my generated tests get saved?
Your project's existing tests directory (auto-detected). Same convention as the other tailtest variants. The MCP server records the source-to-test mapping in .tailtest/session.json.
I'm on Cline in JetBrains. Does it work?
Yes. Cline's JetBrains plugin uses the same MCP server architecture as the VS Code extension. tailtest-cline runs identically in both.