test-prerequisite-detection

Test failure classification analyzes error output and test file markers to categorize failures into 'Prerequisite', 'Feature', 'Test Invalid', or 'Environment' types, distinguishing genuine bugs from setup problems. This reduces debugging time by pinpointing the exact root cause.

Test debt refers to persistent prerequisite failures that block testing. This Skill tracks recurring prerequisite blockers in a dedicated JSON file, managing and recording these failures for efficient resolution and continuous visibility.

Environment issue detection identifies infrastructure-level problems like port conflicts or zombie processes by analyzing test error output. It recognizes these specific failures and suggests automated recovery actions to restore the testing environment.

Yes, test failure classification operates without external dependencies. It utilizes heuristic pattern matching on error output and test file markers internally to categorize failures and generate structured output for clear identification.

Automated tests fail when login prerequisites fail because the feature test cannot execute properly. This Skill analyzes error output to determine if a prerequisite failed, a UI element is missing, or a port conflict prevents execution.

Yes, you can automate recovery for environment issues. The Skill identifies infrastructure-level problems during classification and suggests automated recovery actions to resolve environment failures and allow test execution to proceed.