SpurQuality AI Testing Assistant

Sign in to SpurQuality once and both its QA Agents and Test Management tools become available to your AI assistant — GitHub Copilot (agent mode) and Claude Code — over MCP. No separate setup for each tool family, no juggling two extensions.

What you get

QA Agents

Generate, automate, explore, heal, execute and triage tests from chat:

• Setup & Planning — plan coverage before you write anything
• Generate & Author — turn requirements or a feature file into tests
• Automate — produce automation scripts from manual steps
• Explore & Discover — find existing tests, locators and coverage gaps
• Execute & Triage — run suites and sort out what actually broke
• Heal / Auto-Heal — fix a test broken by a UI/locator change
• Performance, Security, API, Mobile, Accessibility & Visual — testing types beyond plain functional UI tests
• Unit & Code Quality, Knowledge & Insights — code-level tests and reporting on what you have

Test Management

Full CRUD-style access to your SpurQuality test management data — test cases, executions, test plans, preconditions, stories, epics, bugs, projects, requirements, and report generation — as individual, discoverable MCP tools.

The sidebar

The SpurQuality activity bar icon opens three panels:

• Status — sign-in state, which servers are configured for this workspace, and quick actions
• QA Agent Tools — every QA Agents tool, browsable by category or by a plain-language search ("heal a broken locator")
• Test Management Tools (MCP) — the same, for the Test Management catalogue

Selecting a tool opens a reference panel with what it does, when to use it (and when not to), its parameters, and a ready-to-copy prompt — nothing here executes a tool directly; that always happens through the AI assistant.

Getting started

1. Install the extension and click Sign in in the SpurQuality sidebar (or run SpurQuality: Sign in with SpurQuality from the Command Palette).

2. Approve the request in your browser. If your account belongs to more than one organization, pick one there.

3. The extension writes the MCP server entries for this workspace:

   File	Used by
   .vscode/mcp.json	GitHub Copilot
   .mcp.json	Claude Code

   Both are gitignored automatically — they hold live credentials.

4. Open chat in Copilot (agent mode) or Claude Code and ask for what you need, e.g. "Generate BDD scenarios for the checkout flow" or "Show me the test cases linked to this story."

Credentials are stored once per machine (OS keychain); the MCP config is written per workspace. Opening a new project? Run SpurQuality: Write MCP Configuration to This Workspace — no need to sign in again.

Requirements

• VS Code 1.100 or later
• A SpurQuality account
• GitHub Copilot (agent mode) and/or Claude Code, to actually run the tools

Settings

Privacy

This extension only writes configuration your AI assistant needs to reach SpurQuality's MCP servers. It does not run or modify tests on its own — every action happens through the assistant you're already using.