What is issues-test-failure-diagnosis?

A process for investigating failed tests and documenting their root causes. It separates production bugs, incorrect tests, missing data, and environment problems before choosing a fix.

Use it to diagnose Maven test failures, inspect Surefire reports and stack traces, fix the correct source or test file, and write a report of the cause, changes, and verification.

It prevents symptoms from being mistaken for causes and discourages hiding failures by disabling tests or adding delays. Re-running tests from one case to the full suite provides evidence that the fix works.

issues-test-failure-diagnosis — Cursor rule for Cursor by vepo: A process for investigating failed tests and documenting their…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/vepo/issues/issues-test-failure-diagnosis

Clone the repo

git clone --depth 1 https://github.com/vepo/issues

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/vepo/issues/issues-test-failure-diagnosis.svg)](https://agentmods.dev/rules/vepo/issues/issues-test-failure-diagnosis)

Your own site

<a href="https://agentmods.dev/rules/vepo/issues/issues-test-failure-diagnosis"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-test-failure-diagnosis.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 339 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00339
Opus 5	$0.00000	$0.00169
Sonnet 5	$0.00000	$0.00068
Haiku 4.5	$0.00000	$0.00034

Measured 5d ago against content hash c58d35b5a56b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issues-test-failure-diagnosis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/issues-test-failure-diagnosis.mdc · 49 lines

What it actually says

Test failure diagnosis

When tests fail during development or via fix_tests.md:

1. Collect evidence

Surefire report: target/surefire-reports/*.txt
Console stack trace from mvn test -Dtest=Class#method

2. Classify

Type	Signs	Action
Production bug	Wrong status, missing validation	Fix `src/main`
Test bug	Wrong assertion, stale fixture	Fix test
Data/setup	Missing seed, wrong `Given`	Fix test data
Environment	DB, port, Quinoa	Fix config or document prerequisite

3. Fix one root cause at a time

Re-run single test: mvn test -Dtest=ClassName#methodName
Then class, then full mvn test

4. Report template

After fixing, write reports/{NNN}-test-failure-{Class}-{method}-{timestamp}.md:

# Test failure report

- **Test:** ClassName#methodName
- **Root cause:** (one sentence)
- **Fix:** (files changed)
- **Verify:** mvn test -Dtest=... (pass)

Rules

Domain spec wins over test expectation when behaviour is specified.
Never @Disabled or Thread.sleep() as fixes.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 49 lines · 0 tokens per session scan A c58d35b5a56b

Subscribe to this mod's changes

issues-test-failure-diagnosis is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 339 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

angular quarkus

issues-test-failure-diagnosis