test-fixing

Identify and fix failing tests with grouped error patterns.

4|1|Updated Apr 4, 2024
One-click install
npx skills add https://github.com/maraxen/praxis --skill test-fixing-maraxen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-fixing
Source: https://github.com/maraxen/praxis/tree/main/.agent/skills/test-fixing
Command: npx skills add https://github.com/maraxen/praxis --skill test-fixing-maraxen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and fix failing tests by grouping errors smartly, reducing debugging time and improving stability of the codebase.

Core Features & Use Cases

  • Initial Test Run: Run the test suite to enumerate failures and collect error patterns.
  • Smart Error Grouping: Cluster failures by type, module, and root cause to prioritize fixes.
  • Systematic Fixing Process: Follow a guided workflow to implement minimal, targeted changes and re-run tests.
  • Final Verification: Validate all tests pass and report any regressions for CI.

Quick Start

Run the test suite and start the guided process to identify, group, and fix all failing tests.

Frequently Asked Questions about test-fixing

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

FAQPage Schema
How do I fix failing tests faster when debugging a large test suite?

Fix failing tests by running an initial test suite to collect error patterns, then applying smart error grouping. This clusters failures by type, module, and root cause to prioritize fixes and systematically implement minimal, targeted changes.

What is the best way to group test failures by root cause in a CI pipeline?

Group test failures by root cause using structured error grouping, which clusters failures by type and module. This enables a prioritized remediation workflow that ensures stable test suites through repeatable verification across CI pipelines.

Can I use this test-fixing workflow for local development cycles and pytest?

Yes, you can use this test-fixing workflow for local development cycles and pytest. It applies to test suites of varying sizes across modules, CI pipelines, and local development, guiding you through systematic fixing and final verification to report regressions.

How do I start a systematic process to debug and fix failing tests?

Start a systematic process to debug and fix failing tests by running the test suite to enumerate failures and collect error patterns. Follow the guided workflow to implement minimal, targeted changes, re-run tests, and validate all tests pass for final verification.

Does this approach help identify regressions when fixing failing tests?

Yes, this approach helps identify regressions when fixing failing tests. The final verification step validates that all tests pass and explicitly reports any regressions for CI, ensuring the overall stability of the codebase.