x-troubleshoot-operations

Systematic troubleshooting diagnoses and fixes software issues by reproducing, locating, understanding, fixing, and verifying failures. It applies to compilation errors, test failures, build issues, and runtime exceptions across typical development workflows.

To fix code bugs without regressions, write a bug-reproducing test before applying any code changes. This fix-first-test pattern ensures the original failure is captured and verified against the project's full test suite after the correction.

Yes, you can use this troubleshooting workflow for runtime exceptions and performance problems. It is designed for broad applicability across development, QA cycles, and incident investigations to diagnose and fix typical software project failures.

The best way to locate and understand compilation errors is through a repeatable troubleshoot workflow. This approach guides you step by step through reproducing the failure, localizing the fault, applying code changes, and verifying the fix.

To start troubleshooting a failing scenario, provide the failing scenario details and let the workflow guide you. The process moves sequentially through reproduction, fault localization, understanding the issue, implementing the fix, and full verification.