skills.rest
DavidTeju
DavidTejuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-debugging-without-hacking

Diagnose failing tests through root-cause analysis and isolated execution.

9|2|Updated Mar 5, 2026
Search Tags:#workflow#vitest#testing#debugging#quality-assurance#root-cause#bug-classification
One-click install
npx skills add https://github.com/DavidTeju/shared-skills --skill test-debugging-without-hacking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-debugging-without-hacking
Source: https://github.com/DavidTeju/shared-skills/tree/main/skills/test-debugging-without-hacking
Command: npx skills add https://github.com/DavidTeju/shared-skills --skill test-debugging-without-hacking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic approach to fix failing tests by identifying root causes instead of hacking tests or altering expectations.

Core Features & Use Cases

  • Stepwise debugging methodology from reading tests to verifying fixes
  • Clear decision framework to classify bugs as test or service
  • Practical patterns for common failures like missing mocks, assertion mismatches, and mock state pollution

Quick Start

Follow the guided debugging workflow to identify root causes, isolate failures, and implement fixes without changing test assertions.

Frequently Asked Questions about test-debugging-without-hacking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix failing tests without hacking the test expectations?▼

Fix failing tests by tracing execution and isolating failures to identify the root cause, rather than altering test assertions. This debugging workflow classifies bugs as test or service issues and applies targeted fixes.

What causes test failures that only happen in combination or after changes?▼

Test failures in combination or after changes are often caused by mock-state pollution or complex service interactions. A systematic debugging approach isolates the failure to classify whether the bug is in the test or the service.

How do I debug mock state pollution in vitest?▼

Debug mock state pollution by running isolated tests and tracing execution to locate the root cause. A structured debugging workflow identifies whether missing mocks or assertion mismatches are polluting the test state.

What is the best way to classify bugs as test or service issues during debugging?▼

The best way to classify bugs is using a clear decision framework that traces execution and reads failing tests. This workflow distinguishes whether failures stem from the test suite or complex service interactions.

How do I trace execution to resolve complex service interaction failures?▼

Resolve complex service interaction failures by reading failing tests, tracing execution, and running isolated tests. This stepwise debugging methodology applies a robust workflow to identify and fix the root cause.

Related Skills

Explore More Software Engineering Skills→
andrew-starosciakandrew-starosciak
2

iterative-retrieval

Refine subagent context through a four-stage iterative retrieval loop.

Community
Advanced
withzombieswithzombies
80

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

Community
Advanced
UvRoxxUvRoxx
8

midnight-test-runner

Run and debug Midnight contract tests using Vitest simulators.

Community
Intermediate
hoanghd218hoanghd218

debug

Trace bugs to root causes using systematic debugging phases and validation.

Community
Advanced