nextjs-testing
Testing patterns for Next.js + TypeScript projects with React Testing Library
Найдите подходящую возможность для вашего агента.
Testing patterns for Next.js + TypeScript projects with React Testing Library
Refine requirements from discoveries during TDD/BDD implementation. Captures edge cases, race conditions, and business rules discovered by developers. Enables requirements refinement loop. Use when developers discover missing requirements during coding.
Test case execution guide for Saudi telehealth patients in Dr. Sophia AI. Covers 5 test cases (Ahmed, Fatima, Abdullah, Sara, Aisha), data separation principles (historical vs current symptoms), success criteria, critical safety validation. Use when testing Saudi patient consultations, running diagnostic accuracy tests, validating AI responses, or checking allergy/safety protocols.
Analyze a Java class and scaffold a JUnit 5 test with proper structure and assertions
This skill should be used when the user asks about "Rails testing", "RSpec", "Minitest", "request specs", "system specs", "FactoryBot", "fixtures", "test coverage", "testing controllers", "testing models", "integration tests", or needs guidance on writing effective tests for Rails 7+ applications.
Write focused, strategic tests for core user flows with behavior-based testing, clear naming, and proper mocking of external dependencies. Use this skill when writing unit tests, integration tests, or end-to-end tests. When working on files in tests/, __tests__/, spec/, or *.test.ts, *.spec.ts files. When deciding what to test during feature development. When naming test cases descriptively. When mocking databases, APIs, or external services. When focusing on testing behavior rather than implementation details.
Generator สำหรับสร้าง Bruno API test collections อัตโนมัติจาก OpenAPI specs หรือ endpoint definitions
Use when testing "web application", "Playwright", "browser automation", "UI testing", "frontend testing", "E2E testing", "end-to-end tests", or asking about "test local webapp", "browser screenshots", "DOM inspection"
Use when implementing features or adding functionality - dispatches incremental-tdd-agent that enforces ONE test at a time, preventing batch test writing that defeats incremental design discovery. Maintains discipline through entire feature implementation (10+ test cycles)
Guides strict TDD (red/green/refactor), prioritizing domain unit tests and small steps.
Complete Behavior-Driven Development workflow coordinating SCENARIO → STEP DEFINITIONS → IMPLEMENT → REFACTOR cycle with Given/When/Then scenarios. Use when writing BDD tests or implementing features from user stories.
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
Compares code implementation against specifications and requirements. Verifies functional requirements, non-functional requirements, acceptance criteria, and technical specifications are met. Returns structured reports of specification gaps and misalignments.
API integration testing with Supertest and Vitest. Use when testing API endpoints.
Use when implementing features/bugfixes to enforce strict TDD discipline - enforces RED (write failing test), GREEN (minimal code), REFACTOR cycle with no exceptions. Prevents "test after" trap, catches rationalizations. Activates when user says "implement", "let's code", "write this feature", mentions "TDD", or during spec-driven execution phase.
Use this skill when implementing any feature, bug fix, or plan task. Triggers on "write tests", "add a test", "do TDD", "test-driven", "implement with tests", "implement task", or when dispatched as a subagent for plan execution. Write test first, watch it fail, write minimal code to pass.