Aplica padrões de excelência em testes com NestJS e Jest seguindo Clean Architecture, DDD e boas práticas de testabilidade. Use quando criar ou refatorar testes unitários, de integração ou E2E em projetos NestJS.
Verify test execution by replaying trajectory and checking script coverage. Ensures tests actually happened as recorded and scripts cover all test cases. WHEN TO USE: - After tests claim to pass (verify they actually ran) - Before marking ticket complete (audit trail) - When reviewing someone else's work - User says "validate", "verify tests", "check coverage" - Periodic audit of test integrity CHECKS: 1. TRAJECTORY - Steps match recorded actions 2. EVIDENCE - Screenshots, logs, outputs exist 3. COVERAGE - Scripts test all cases from 3-spec.md 4. COMPLETENESS - All required tests have trajectory
Complete Test-Driven Development workflow coordinating RED → GREEN → REFACTOR → COMMIT cycle with requirement traceability. Use this when implementing a requirement (REQ-*) or adding new functionality.
Guide for writing integration tests for API endpoints. Use when creating endpoint tests, testing validation, or asserting JSON responses.
Unit testing best practices, patterns, and strategies for comprehensive test coverage
Run TDD cycle for feature implementation. Use when implementing features with RED-GREEN-REFACTOR, running test-driven development, automating TDD workflow, or ensuring test-first development.
Cross-language testing patterns: unit, integration, E2E testing strategies. Use when: writing tests, setting up test infrastructure, or improving coverage. Triggers: "test", "testing", "unit test", "integration test", "e2e", "coverage", "mock", "fixture".
Enforce Test-Driven Development with strict Red-Green-Refactor cycle using integration tests. Auto-triggers when implementing new features or functionality. Trigger phrases include "implement", "add feature", "build", "create functionality", or any request to add new behavior. Does NOT trigger for bug fixes, documentation, or configuration changes.
Use when working with .rb files, Ruby gems, or implementing Ruby features. Covers Ruby idioms, naming conventions, enumerable patterns, service objects, error handling, and RSpec testing.
Python unit testing patterns for pytest, including test file structure, fixtures, mocks, and coverage strategy. Use when asked to write tests (unit/integration) for any Python module, function, class, or method.
General-purpose patterns for reliable browser automation (selectors, waiting, scrolling, overlays, HITL).
Writing Probitas scenarios. MUST BE USED when writing/editing E2E tests, creating scenarios, or working with *.probitas.ts files.
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Fix failing tests based on failure reports, verify fixes, and iterate until all tests pass. This skill should be used after test-executor generates failure reports, providing systematic debugging and fixing strategies that work with any framework or language.
테스트 케이스를 생성합니다. "테스트 작성", "TC 만들어", "write test" 요청 시 사용합니다.
Optional end-to-end tests in Godot using GdUnit4
Runs tests for Spring Boot modules with proper Java version handling. Use when testing code changes, debugging test failures, or verifying module functionality.
Use when writing unit tests, integration tests, or end-to-end tests in Python. Also use for implementing test fixtures, mocking, parametrization, async testing, or coverage analysis. NOT when using other testing frameworks (unittest, nose) or testing non-Python code.
Jest and React Native Testing Library patterns. Use when writing component tests.
Automatically applies when writing pytest tests. Ensures proper use of fixtures, parametrize, marks, mocking, async tests, and follows testing best practices.
生成并配置用于新华三技术有限公司H3C网络设备自动化的 pytest `conftest.py`，`conftest.py`文件主要负责测试背景搭建和测试背景清理。
