testing-code
Generates unit and integration tests using industry-standard frameworks (Jest, Vitest, Pytest). Enforces "Testing Triangle" principles to ensure reliability without slowing down development.
Discover data ai testing skills, compare source repositories and read the instructions for each workflow.
Generates unit and integration tests using industry-standard frameworks (Jest, Vitest, Pytest). Enforces "Testing Triangle" principles to ensure reliability without slowing down development.
Rules for when and how to run tests during development
Core testing principles applying to all unit and integration tests
Complete patterns for testing async Python code with pytest: pytest-asyncio configuration, AsyncMock usage, async fixtures, testing FastAPI with AsyncClient, testing Kafka async producers/consumers, event loop...
Unit test patterns using nock for HTTP mocking without credentials
Complete pytest configuration: pyproject.toml setup, custom markers registration, test discovery patterns, plugin configuration, environment-specific settings. Includes conftest.py hierarchy, fixture scoping, a...
Run targeted Playwright E2E flows for auth, scheduling, and onboarding. Use when the user asks for E2E smoke tests or specific flow validation.
Systematic approaches to proving a fix works and preventing regression
Open multiple browser tabs and compare content, behavior, or visual appearance across pages. Use when comparing staging vs production, A/B testing page variants, testing cross-browser consistency, verifying con...
The Unified Testing Constitution and "Junie-Mode" protocol for reproducing, fixing, and verifying bugs.
Use when you have implemented a new screen or widget that needs widget tests
Gate 4a validation: Unit test creation and nock-only enforcement
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.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
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.
HTTP mocking with nock - the only allowed mocking library
Generate comprehensive JUnit 5 test cases for Java code with proper mocking and coverage. Use when writing tests, creating unit tests, generating test cases, adding JUnit tests, setting up Mockito mocks, writin...
Captures screenshots of web application pages using Playwright. Use when the user asks to take screenshots, capture page visuals, document UI states, or create design documentation. Supports full-page screensho...
Expert skill for implementing Behavior-Driven Development (BDD) testing using Cucumber and other BDD frameworks. Helps teams bridge the gap between business requirements (user stories, acceptance criteria, shar...
開發前端頁面時,為可互動元素添加 testId 以支援 E2E 測試
Create factory fixture patterns for customizable test setup with variations. Use when building reusable test fixtures with multiple configurations, creating parameterizable mocks, or implementing test data buil...
Follows a feature specification with TDD approach, progress tracking, and phase confirmations. Takes a spec file path as argument. Use when user wants to implement a spec or invokes /spec-implement.
Create pytest fixtures following project patterns including factory fixtures, async fixtures, and multi-layer organization. Use when setting up test fixtures, creating test data, organizing test utilities, or s...
Expert guidance for software testing and quality assurance. Use when the user asks to write tests, create test plans, review code for bugs, perform code reviews, write test cases, set up testing frameworks, deb...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.