systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Découvrez les skills tools testing, comparez leurs dépôts et consultez leurs instructions.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Enforces the discipline of thinking about tests, features, and maintainability BEFORE writing implementation code. Use when starting new classes/methods, refactoring existing code, or when asked to "think about...
Testing patterns and principles. Unit, integration, mocking strategies.
Guides widget test patterns: BLoC testing, user interactions, state changes, material app setup. Use when writing widget tests, testing UI components, or validating widget behavior.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Master mocking strategy for pytest: when to use autospec=True vs manual mocks, AsyncMock patterns for async code, mock builders and factories, and what should NEVER be mocked. Includes type-safe mock creation p...
Pytest fixture patterns for Textual TUI application testing. Creates reusable test setup code including app factories, Pilot wrappers, mock fixtures, and async patterns. Use when: setting up test infrastructure...
Guide test placement in correct test pyramid layer (unit/integration/e2e). Use when creating new test files, deciding test layer, organizing test structure, or determining fixture scope. Analyzes mocking patter...
Écrit et exécute les tests pour valider l'implémentation. Utiliser après l'implémentation du code, quand on a besoin de vérifier que le code fonctionne, ou avant les code reviews. Peut aussi être utilisé en mod...
How to test domain models effectively: value object testing (immutability, validation), entity testing (identity, business logic), domain exception testing, aggregate testing, high coverage patterns (95%+), and...
Run tests for the current project
Test fixture organization, sanitization, and realistic response patterns
Automates form validation testing by submitting invalid data and capturing error states using Playwright browser automation. Use when you need to "test form validation", "check validation errors", "test invalid...
Captures screenshots at multiple viewport breakpoints for responsive design validation and documentation. Use when you need to test responsive layouts, validate mobile/tablet/desktop views, document design syst...
Gate 5 validation: Test execution and 100% pass rate requirement
Execute tasks from a feature spec one at a time, updating living documentation as you go. Use after /interview to implement the planned feature.
Enforces test implementation requirements: real dependencies, no mocks/stubs unless approved. Use when writing tests, reviewing test implementations, or ensuring tests use real functionality.
Write integration tests for Kafka producers and consumers using testcontainers. Use when testing producer/consumer workflows, verifying message ordering, testing error scenarios, and validating exactly-once sem...
Test-Driven Development workflow - use only when explicitly requested. Write failing test first, verify it fails, write minimal code to pass, refactor while keeping tests green
Run the right tests for changes and keep coverage expectations. Use when modifying code or tests, or when debugging failures.
Set up async tests with proper fixtures and mocks using pytest-asyncio patterns. Use when testing async functions, creating async fixtures, mocking async services, or handling async context managers. Covers @py...
Generate MSTest + Moq unit tests for Notebook Automation, following existing patterns in src/c-sharp/NotebookAutomation.Tests.
Guidance for running and updating tests in this repository.
Monitors and analyzes network traffic during browser automation workflows using Playwright MCP tools. Use when investigating API behavior, debugging failed requests, performance analysis, or checking network ac...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.