testing-strategies
Comprehensive testing approaches for reliable software
Comprehensive testing approaches for reliable software
Use at session start - establishes Shannon Framework workflows including mandatory 8D analysis before implementation, NO MOCKS testing enforcement, wave-based execution for complexity >=0.50, and automatic Serena MCP checkpointing. Prevents under-estimation and ensures quantitative rigor. Trigger keywords: shannon, specification, complexity, wave, checkpoint, functional testing.
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests with quantitative reliability tracking
Jest testing strategies, test organization, factory patterns for test data, mocking strategies for authentication and external services, real-time message processor testing, test-driven development workflow, unit vs integration testing, fake timer usage for time-dependent tests, and testing best practices for ree-board project
Unit, widget, integration, and golden test patterns with mocking strategies
Expert in Jest testing framework, advanced mocking strategies, snapshot testing, async patterns, TypeScript integration, and performance optimization
Guide experienced developers through RED phase of TDD cycle - writing failing tests and verifying expected failures
Create maintainable and reusable Page Object Models (POMs) for Playwright tests. Generates TypeScript classes that encapsulate page-specific locators and actions, following the Page Object Model design pattern with data-testid locators exclusively.
Generate comprehensive test suites for Scrapy spiders, pipelines, and middlewares when implementing tests or improving coverage. Creates unit tests, integration tests, and contract tests with proper fixtures and mocking.
Create Vitest unit tests following project patterns. Use when writing tests for functions, components, models, or route loaders/actions.
Improve acceptance criteria so they are testable, unambiguous, and complete.
LUA testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
自动化测试专家,精通单元测试、集成测试、E2E测试和性能测试。能够设计和实施全面的测试策略,确保软件质量和可靠性。
Write unit tests and integration tests for Go code using testify, go-sqlmock, and mockery. Use when writing tests, creating test files, or testing repositories, use cases, and handlers.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
Generates integration tests for frontend → backend → Genkit flow connections. Use when creating E2E API tests.
This skill should be used when the user asks about testing Rails applications, Minitest, test-driven development (TDD), unit tests, integration tests, system tests, fixtures, factories, mocking, stubbing, test coverage, continuous integration, test organization, or Rails testing best practices. Also use when discussing testing philosophy, test speed, or debugging failing tests. Examples:
Apply when implementing new features, fixing bugs, or refactoring code. TDD ensures tests drive design and all code is covered.
Skill with external file references for testing detection
Mutation testing with Stryker to verify test quality by introducing code mutations and measuring detection rates