Writes comprehensive test cases including unit tests, integration tests, and E2E tests. Use when implementing test requirements from tasks. Creates tests that cover happy paths, edge cases, error conditions, and follow testing best practices.
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.
Write E2E tests using Playwright with Cucumber/Gherkin for this project. Use when creating tests, writing test cases, testing UI flows, API testing, or when user mentions e2e, playwright, cucumber, gherkin, bdd, test automation, or QA.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Python testing best practices with pytest. Covers unit, integration, async tests, mocking, fixtures. Triggers: "write tests", "add tests", "test coverage", "pytest", "tests"
检查Acceptance Criteria格式和完整性，验证是否符合Given-When-Then结构、覆盖正常流程/边界条件/异常场景。适合在为User Story编写AC后、准备测试用例前使用，当需要验收AC质量时。帮助不熟悉BDD的PM/BA确保AC明确、可测试、覆盖完整，避免遗漏关键场景。
Autonomously performs the TDD loop (Red-Green-Refactor) for a single plan item.
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.
Run test_local.sh and analyze results including PNG outputs, execution logs, memory usage CSV, and performance metrics. Identifies issues like missing data points, memory spikes, or performance problems. Use after code changes to verify functionality.
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 immediately when user mentions: "テスト", "test", "BDD", "feature", "フィーチャー", "scenario", "シナリオ", "Given", "When", "Then", "カバレッジ", "coverage", "pytest-bdd", "Gherkin". MUST USE this skill for: - Creating BDD feature files with Gherkin syntax - Implementing step definitions with pytest-bdd - Designing test scenarios and fixtures - Any work in tests/ directory
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
End-to-end testing with Playwright. Use when writing E2E tests, implementing page objects, setting up test fixtures, handling authentication in tests, adding visual regression testing, or configuring E2E tests for CI. Covers when to use E2E vs integration tests, critical path identification, page object pattern, test isolation, and CI considerations.
Write comprehensive test coverage across unit, integration, regression, end-to-end, and manual tests. Watch for deprecation warnings in test output and address them immediately. Use when writing tests, implementing features, or before creating pull requests.
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
Review pages visually and test accessibility using agent-browser CLI
