What problem does it solve? When a .NET integration or E2E backend test fails, it is tempting to guess the cause from the exception type or rerun the whole suite. This Skill enforces an evidence-first diagnostic workflow that pinpoints the exact failing assertion, correlates test-runner, application, database, and container logs, and classifies the root cause before any code change is proposed. ## Core Features & Use Cases - Evidence-ordered diagnosis: Walks through test identity, assertion details, test-runner output, application-host logs, and dependency logs in a fixed order so infrastructure noise does not hide a product assertion. - Failure classification: Assigns exactly one primary classification (assertion/product behavior, test setup/isolation, startup/pipeline, database/infrastructure, external dependency, or timing/concurrency) with supporting evidence. - Structured diagnosis report: Produces a standardized report with verdict, assertion evidence, log evidence, root cause, discriminating check, smallest fix, and validation steps. - Use Case: A CI run of ECommerceApp.Web.IntegrationTests fails with a generic HTTP 500. Use this Skill to extract the exact assertion from the TRX log, correlate the server exception by timestamp, classify it as an application startup error, and identify the smallest fix. ## Quick Start Ask the assistant to diagnose the failing integration test by pasting the dotnet test failure output or the path to the captured log file.
