lsp-test-correlation

Files (1)

• SKILL.md

SKILL.md (first lines)

> Requires the agent-lsp MCP server.

# lsp-test-correlation

Discover which tests cover a source file, then run only those tests. Faster
than running the full suite when you've changed one or two files and want
targeted feedback.

## When to use

- After editing a source file: "Which tests do I need to run for this change?"
- Before committing: run only the tests that cover what you touched
- Debugging a failure: find which test file corresponds to a broken source file
- Code review: understand what test coverage exists for a file before merging

Use `/lsp-verify` instead when you want to run the full suite and check all
three layers (diagnostics + build + tests). Use this skill when you want fast,
scoped test execution.

---

## Workflow

### Step 1 — Find correlated test files

Call `get_tests_for_file` for each edited source file:

```
mcp__lsp__get_tests_for_file({ "file_path": "/abs/path/to/source.go" })
```

Returns the test files that correspond to the source file. For multiple edited
files, call once per file.

**If no test files are returned:** the source file may have no dedicated test
file, or the mapping is not resolvable (e.g. integration tests in a separate
directory). See Step 2 for fallback.

### Step 2 — Enumerate test functions (fallback or enrichment)

If `get_tests_for_file` returns test files, use `find_symbol` to list
the test functions defined in those files:

```
mcp__lsp__find_symbol({ "query": "Test" })
```

Filter results to the correlated test files from Step 1. This gives you the
specific test function names to run rather than the whole test file.

**Fallback (no test files found):** query `find_symbol` for test
functions that contain the changed symbol's name:

```
mcp__lsp__find_symbol({ "query": "Test<ChangedFunctionName>" })
```

This catches cases where `get_tests_for_file` misses indirect coverage.

### Step 3 — Report the correlation map

Before running, report what was found:

```
## Test correlation for <file>

Source file: internal/tools/analysis.go
Test files:
  → internal/tools/analysis_test.go
     Tests: TestHandleGetCodeActions, TestHandleGetCompletions, TestHandleGetDocumentSymbols

No correlated test files found for: internal/lsp/normalize.go
  → Fallback: TestNormalizeCompletion, TestNormalizeDocumentSymbols (from workspace symbol search)
```

If the user provided `run=true` or asks to run, proceed to Step 4. Otherwise
stop here and let the user decide.

### Step 4 — Run correlated tests

Run only the correlated test files or functions. Scope as tightly as possible:

**Go — run specific package:**
```
mcp__lsp__run_tests({ "workspace_dir": "<root>", "test_filter": "TestHandleGetCodeActions|TestHandleGetCompletions" })
```

If `run_tests` does not support `test_filter`, pass the package path instead of
the workspace root to narrow scope. The test output will be smaller and faster
than running `./...`.

**Output handling:** If test output is large, do not read it in full. Search
for failures:
```
grep -E "^(FAIL|--- FAIL)" <output_file>
```

### Step 5 — Report results

```
## Test Results

Ran 3 tests in internal/tools/analysis_test.go

PASSED (2):
  TestHandleGetCodeActions
  TestHandleGetCompletions

FAILED (1):
  TestHandleGetDocumentSymbols — expected 3 symbols, got 2 (analysis_test.go:87)

Recommendation: Fix TestHandleGetDocumentSymbols before committing.
```

---

## Multi-file workflow

For changes spanning multiple source files:

From blackwell-systems/agent-lsp, MIT.

More from blackwell-systems/agent-lsp