smoke-suite-debugging
Use this when smoke tests fail (binary/web assets, Playwright setup, server lifecycle, ports, env vars).
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Use this when smoke tests fail (binary/web assets, Playwright setup, server lifecycle, ports, env vars).
Use this skill to diagnose and repair broken tests with a methodical, surgical approach. AUTO-ACTIVATE when user mentions (FR/EN): - test cassé, broken test, failing test, test fail, test échoue - erreur test, test error, assertion failed, timeout test - réparer test, fix test, corriger test, debug test - npm test fail, jest error, test suite failed AGENTS: Specialized agents (backend-specialist, frontend-specialist, database-specialist) MUST invoke this skill when asked to fix tests. Use: Skill("test-doctor") CRITICAL: NO mass corrections. ONE test at a time with validation. ALWAYS diagnose before fixing. ALWAYS consult DONT_DO.md first. Context: 1211 test files, 5561/6101 passing (540 failing). Stack: Jest, React Testing Library, Prisma, Next.js 15, TypeScript 5.
Create mocks using mockall and trait-based abstractions. Use when unit testing code with external dependencies.
Component documentation, visual testing, interaction testing
TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.
End-to-end testing using Playwright MCP. Automate user workflows, take screenshots, validate UI/UX, perform visual regression testing, and verify complete user journeys. Use after feature implementation or before deployment.
"Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements."
How to structure applications for optimal testability in Clojure and Clojurescript, along with how to use guardrails and fulcro-spec to do the actual testing. You MUST use this skill when writing Clojure and Clojurescript if fulcro-spec is a dependency.
Use when writing Rails tests - enforces fixtures-only, integration-style controller tests, Current context setup, simple naming, and Minitest syntax
Use to assess non-functional requirements (security, performance, reliability, maintainability) through E2E integration testing patterns.
Generate test scenarios for Fujian Mahjong game logic. Use when you need test cases for win detection, Gold substitution, calling validation, edge cases, or scoring calculations.
Run tests in the actual execution environment, not just where they compile - TDD's "watch it fail" step is meaningless if tests skip or can't run where code will execute
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Tiered testing strategy (UI mock, auth stub, full-stack), fixtures, mocks, and test configuration. Handles test setup, Playwright E2E tests, pytest backend tests, mocking strategies, and CI test configuration. Use when working with tests, test setup, mocking strategies, or CI test configuration, or when user mentions test patterns, auth stub, fixture loaders, Playwright tests, test failures, tiered testing, UI mock, E2E tests, pytest, vitest, or debugging test issues.
Use when testing async code with Swift Testing. Covers confirmation for callbacks, @MainActor tests, async/await patterns, timeout control, XCTest migration, parallel test execution.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first