skills.rest
gustavop-dev
gustavop-devCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fix-broken-tests

Diagnose and repair failing software tests with targeted code changes.

Updated Jun 1, 2024
Search Tags:#automation#testing#ci/cd#debugging#pytest#bug fixing#playwright
One-click install
npx skills add https://github.com/gustavop-dev/projectapp --skill fix-broken-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-broken-tests
Source: https://github.com/gustavop-dev/projectapp/tree/main/.agents/skills/fix-broken-tests
Command: npx skills add https://github.com/gustavop-dev/projectapp --skill fix-broken-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of diagnosing and fixing broken tests efficiently, reducing debugging time and maintaining reliable test suites.

Core Features & Use Cases

  • Test Reproduction & Diagnosis: Reproduce and analyze failing tests across backend and frontend codebases to identify root causes.
  • Targeted Fixes: Apply minimal code changes to resolve test failures while avoiding unnecessary modifications to production logic.
  • Regression Verification: Re-run tests with exact commands to verify fixes and ensure stability in specific test scenarios.
  • Use Case: Suppose a developer encounters a failing pytest in the backend. Use this Skill to automatically analyze the failure, apply necessary patches, and verify the fix with precise commands.

Quick Start

Reproduce the failed test, analyze the issue, fix the code, and run the specific command to confirm the fix.

Frequently Asked Questions about fix-broken-tests

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

FAQPage Schema
How do I fix failing pytest tests in my backend without modifying production logic?▼

To fix failing pytest tests, the Skill reproduces the failure, analyzes the root cause, and applies minimal targeted code changes to resolve the issue without altering backend production logic. It verifies the fix by re-executing exact test commands.

What is the best way to diagnose and repair broken frontend tests?▼

Diagnosing broken frontend tests involves reproducing the failure across your codebase to identify the root cause, applying targeted patches, and running specific commands to verify regression stability.

Can I use this approach to troubleshoot broken Playwright tests?▼

Yes, you can troubleshoot broken Playwright tests by reproducing the failure, analyzing the diagnostic output to locate the error, applying a minimal patch, and running the specific execution command to verify the fix.

Does this test fixing method work for both backend and frontend components?▼

This test fixing method works for both backend and frontend components by efficiently diagnosing failures, applying minimal code changes to repair broken tests, and re-running exact commands to verify stability within software development workflows.

Why should I apply minimal code changes when debugging failing tests?▼

Applying minimal code changes when debugging failing tests ensures you resolve the specific failure without introducing unnecessary modifications to production logic, maintaining test reliability and preventing new regressions.

Related Skills

Explore More Software Engineering Skills→
first-flukefirst-fluke
218

debug-agent

Diagnose software bugs and propose minimal regression-tested fixes.

Official
Advanced
loopyardloopyard
21

fix-bug

Reproduce bugs in Elixir/Mix projects using a test-first workflow.

Official
Intermediate
nashgaonashgao
3

CI Testing Workflow

Automate CI/CD testing pipelines with parallel execution and regression detection.

Community
Advanced
iulianditaiuliandita
2

testing

Provides guidance for writing, debugging, and maintaining automated tests across multiple layers.

Community
Advanced