test-writer
Test generation expertise for Python (pytest) and TypeScript (Jest). Use when writing new tests, improving coverage, or creating test fixtures. Ensures comprehensive coverage including edge cases, error scenari...
Discover data ai testing skills, compare source repositories and read the instructions for each workflow.
Test generation expertise for Python (pytest) and TypeScript (Jest). Use when writing new tests, improving coverage, or creating test fixtures. Ensures comprehensive coverage including edge cases, error scenari...
pytest fixtures and integration testing patterns for Spark applications, including DataFrame assertions and mock data generation.
Generate and run tests for code. Use when creating unit tests, integration tests, or running test suites.
Create integration tests. Use when writing tests, testing features, adding test coverage, or verifying functionality.
Generate comprehensive ServerRequest tests using VaporTesting infrastructure. Use when testing any ServerRequest type (ShowRequest, ViewModelRequest, CreateRequest, UpdateRequest, DeleteRequest) against a Vapor...
Generate comprehensive ViewModel tests with multi-locale translation verification. Use when creating test coverage for ViewModels, especially those with localization.
How to write idiomatic assertions with the Bupkis assertion library for TypeScript and JavaScript
Master Chicago TDD (state-based testing). Verify observable behavior with real collaborators using AAA pattern.
Use when writing UI tests, recording interactions, tests have race conditions, timing dependencies, inconsistent pass/fail behavior, or XCTest UI tests are flaky - covers Recording UI Automation (WWDC 2025), co...
Test harness for executing Speckit workflows non-interactively using subagents. Use when you need to test the complete Speckit pipeline (Phase 0 → Phase 3) or individual phases, validate artifact generation acr...
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking provi...
Run tests, check builds, and validate the application works correctly. Use after making changes.
Write Jest tests for React components in this Gatsby project. Use this skill when creating new tests or improving test coverage. Handles Gatsby-specific mocking and Testing Library patterns.
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.
Complete testing infrastructure and patterns for the monorepo. Use this skill when writing tests, setting up test configuration, troubleshooting test failures, or working with the CI pipeline. Covers vitest con...
Go Constraints. Errors, Context, testify/require, SQLBoiler, Nx Support.
Use when user says "write tests first", "TDD", "test-driven", "tests before implementation", or when implementing a feature where verification is critical. Creates scratchpad, writes failing tests, then iterate...
Use when tests are failing, test quality issues were identified, or user wants to fix/improve specific tests
Enforces project E2E testing conventions using Playwright with custom fixtures, Page Object Model, and authentication contexts.
Enforces project React component testing conventions using Testing Library with proper rendering, user interactions, and accessibility testing.
Enforces project integration testing conventions for facades, server actions, and database operations using Testcontainers with real PostgreSQL.
Enforces project test infrastructure conventions for factories, MSW handlers, mock data, Page Objects, and shared test utilities.
Enforces project shared testing conventions for test structure, file naming, description patterns, assertions, and anti-patterns. This base skill is loaded by all test-type specialists.
Enforces project unit testing conventions for pure functions, validation schemas, and utility modules using Vitest with proper isolation and mocking.
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.