From python-engineering
Analyzes failing test cases to classify failures as test bugs, implementation bugs, or ambiguous. Uses investigative process to verify expectations against code and docs before recommending fixes.
npx claudepluginhub jamie-bitflight/claude_skills --plugin python-engineeringThis skill uses the workspace's default tool permissions.
Analyze failing test cases with a balanced, investigative approach.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Analyze failing test cases with a balanced, investigative approach.
Consult ../python3-core/references/python3-standards.md when shared testing or quality rules from this plugin apply; full standards, graphs, and amendment process are documented there.
When tests fail, there are two primary possibilities:
Assuming tests are wrong by default is a dangerous anti-pattern that defeats the purpose of testing.
For each failing test, ask:
Classify the failure as one of:
| Classification | Meaning |
|---|---|
| Test Bug | Test's expectations are incorrect |
| Implementation Bug | Code doesn't behave as it should |
| Ambiguous | Intended behavior is unclear |
Provide clear explanation including:
Scenario: Test expects calculateDiscount(100, 0.2) to return 20, but it returns 80
Analysis:
Determination: Ambiguous Recommendation: Check documentation or clarify intended behavior
Scenario: Test expects validateEmail("user@example.com") to return true, but it returns false
Analysis:
Determination: Implementation Bug Recommendation: Fix the regex to properly validate email addresses per RFC standards
Scenario: Test expects divide(10, 0) to return 0, but it throws an error
Analysis:
Determination: Test Bug Recommendation: Update test to expect an error, not 0
For each failing test, provide:
Test: [test name/description]
Failure: [what failed and how]
Investigation:
- Test expects: [expected behavior]
- Implementation does: [actual behavior]
- Root cause: [why they differ]
Determination: [Test Bug | Implementation Bug | Ambiguous]
Recommendation:
[Specific fix to either test or implementation]
/python-engineering:test-failure-mindset to set investigative approach for session/python-engineering:comprehensive-test-review for full test suite review