systematic-debugging
Use for bugs/test failures. Reproduce, isolate root cause, fix, and validate with evidence.
Найдите подходящую возможность для вашего агента.
Use for bugs/test failures. Reproduce, isolate root cause, fix, and validate with evidence.
QFAI: Implement acceptance tests from scenarios
Comprehensive web application testing automation using Playwright, including MCP integration, browser automation, E2E testing, visual regression testing, API testing, and CI/CD integration. Use when creating automated tests, setting up test frameworks, debugging test failures, implementing Page Object Model, or integrating testing into deployment pipelines.
Execute tests following TDD cycle: RED (verify test fails) → GREEN (implement to pass) → REFACTOR. Interprets tests.json and performs steps using available tools (browser MCP, API, CLI, etc.). WHEN TO USE: - Starting implementation of a ticket with TDD: yes - After writing test spec (3-spec.md) and tests.json - When user says "run tests", "test this", "TDD cycle" - After fixing a failing test REQUIRES: - Ticket with 3-spec.md - tests.json in .pmc/docs/tests/tickets/T0000N/
Write failing test first, then minimal code to pass. Red-Green-Refactor cycle. Use when: implementing features, fixing bugs, refactoring code. Triggers: "implement", "add feature", "fix bug", "tdd", "test first", "write tests", "test-driven".
Always use this skill when writing or editing software tests!
Guides test creation for Polibase following strict testing standards. Activates when writing tests or creating test files. Enforces external service mocking (no real API calls), async/await patterns, test independence, and proper use of pytest-asyncio to prevent CI failures and API costs.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Write the test first, watch it fail, write minimal code to pass
Execute test_cases.json against educational demos. Systematic testing via Chrome E2E. Single tab, sequential agents. Output: agent_X_tests.json with PASS/FAIL/PARTIAL results. Captures screenshots and identifies bugs/blockers.
Provides unit testing patterns for .NET applications using EF Core In-Memory Provider, AAA structure, test data helpers, and TDD workflows. Use when writing unit tests for services, repositories, or domain logic.
Test writing patterns and TDD workflows. Use when writing tests, creating mocks, following TDD, or debugging test failures.
Comprehensive pytest testing strategies with fixtures, mocking, and TDD patterns. WHEN: Writing pytest tests, creating fixtures, mocking with unittest.mock/pytest-mock, implementing TDD, setting up test configuration (conftest.py, pytest.ini). WHEN NOT: JavaScript tests (use Jest), PHP tests (use PHPUnit), running existing tests without modification.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Debug EUX/EESSI mock issues in melosys E2E tests. Use when: - E2E tests fail with 404 errors from /eux/... endpoints - melosys-api logs show "Kall mot eessi feilet" errors - melosys-eessi logs show NotFoundException for eux endpoints - Adding new EESSI/EUX functionality that requires mock support - Tracing data flow: melosys-api → melosys-eessi → melosys-mock
检查每个US是否有对应的VS,生成覆盖率报告和修复建议。当设计文档创建后、CONSTRAINT验收前使用,避免US→VS覆盖率<100%导致验收失败。
Maintain BDD-style Playwright E2E tests and a human-readable scenario catalog for the Progress Tracker repo. Use when adding/updating scenarios in e2e/SCENARIOS.md, implementing them in e2e/bdd.spec.ts, or fixing flaky selectors across desktop + mobile Playwright projects.
Implement feature code to make BDD scenarios pass. Write production code that satisfies Given/When/Then scenarios. Use after implement-step-definitions when step definitions exist but scenarios are failing.