lsp-test-correlation

Topics in the source

• lsp-test-correlation
• When to use
• Workflow
• Step 1 — Find correlated test files
• Step 2 — Enumerate test functions (fallback or enrichment)
• Step 3 — Report the correlation map
• Step 4 — Run correlated tests
• Step 5 — Report results

Requires the agent-lsp MCP server. 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. 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. -- Call gettestsforfile for each edited source file: 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. If gettestsforfile returns test files, use findsymbol to list the test functions defined in those files: Filter results to the correlated test files from Step 1. This gives you

This is an excerpt. Refer to the complete source and its current requirements.