Guide root-cause debugging for failing or flaky automated tests.
npx skills add https://github.com/mshuffett/dotfiles --skill test-debugging
Please help me install this Agent Skill. Skill: test-debugging Source: https://github.com/mshuffett/dotfiles/tree/main/agents/skills/test-debugging Command: npx skills add https://github.com/mshuffett/dotfiles --skill test-debugging
This Skill addresses the frustration and time loss associated with failing or flaky automated tests by providing a structured workflow to identify and fix the root cause of the failure.
Follow the universal debugging approach outlined in this guide to analyze and fix the failing test.
High-intent search queries and answers about installing and using this skill.
A flaky test indicates an intermittent failure requiring systematic root cause analysis to determine whether the issue originates from the test code, the application code, or the test environment. Creating minimal reproductions helps isolate these inconsistent failures.
Locating the root cause of a test failure involves identifying the failure origin, creating a minimal reproduction, and determining the exact cause before applying a fix. Documenting project-specific patterns during this process improves future troubleshooting.
Creating a minimal reproduction for a failing test involves systematically isolating the variables causing the error to pinpoint the exact origin. This debugging workflow ensures you understand why the test fails before implementing and verifying a fix.
Yes, this root cause debugging workflow is designed for failing and flaky automated tests, including intermittent integration test failures. It guides you through determining whether the failure stems from the test code, application code, or the test environment.
Meta-learning improves software troubleshooting by integrating learnings from debugging sessions to update root memory with universal patterns. Documenting project-specific patterns during root cause analysis refines future test development and maintenance.
derHakenTrace data flow and apply a four-phase process to fix root causes.
xlelibertyAppend project-specific facts and conventions to a centralized MEMORY.md file.
jmaglyAutomate git bisect to find the commit that introduced a regression.
jey3dayoIdentify risks, anti-patterns, and maintenance issues in codebases via static analysis.
