laravel-tester
Generates modern maintainable Laravel applications unit and feature (integration) tests with a focus on performance by default and for best testing style practices.
Find the perfect capability for your agent.
Generates modern maintainable Laravel applications unit and feature (integration) tests with a focus on performance by default and for best testing style practices.
Generate unit tests, integration tests, and test fixtures for code. Supports Jest, Mocha, pytest. Use when writing tests or improving test coverage. This skill provides automated test generation: - Unit tests with AAA pattern (Arrange, Act, Assert) - Integration tests for APIs and databases - Test fixtures and mocks - Edge case identification - Test coverage recommendations Triggers: "generate tests", "create unit test", "add test coverage", "write tests", "テスト生成", "テストコード作成", "カバレッジ向上"
Write technical tickets with structured acceptance criteria and state transitions. Use when user asks to create a ticket, write a task, document a feature, or plan implementation work. Follows [service-name] title convention with detailed acceptance criteria.
Ensures comprehensive test coverage following Rails testing best practices
Comprehensive testing approaches for reliable software
Visual UI testing expert using Playwright MCP for browser automation. Use when testing responsive layouts, verifying UI changes, checking breakpoints, debugging visual/CSS issues, or validating component rendering. Triggers on "test UI", "check layout", "verify design", "responsive", "breakpoint", "visual test", "screenshot".
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
Unit, widget, integration, and golden test patterns with mocking strategies
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 production-ready Playwright E2E tests from natural language specifications or requirements. Creates TypeScript test files following best practices including data-testid locators, proper async/await usage, test isolation, and the AAA (Arrange-Act-Assert) pattern.
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.
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:
在声称工作完成、修复或通过之前使用,在提交或创建 PR 之前。需要运行验证命令并确认输出后才能声称成功。证据先于断言。Use when about to claim work is complete - evidence before assertions always.
质量验收专家,从用户视角验证交付物可用性/正确性/性能/回归。遵循阻断不合格交付、脚本化验证、数据隔离、覆盖验收标准的工程基线。使用 Playwright(E2E)、Jest+Supertest(API)、k6(性能)等工具。适用于收到 QA 部门任务卡(如 CMS-Q-001)或需要验收交付物时使用。
Generates TDD-ready acceptance criteria from screen spec.md. Extracts requirements from features, interactions, flows, and API mappings in Given-When-Then format. Use when creating implementation task specifications.
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
Guide experienced developers through TDD failure scenarios and recovery procedures when tests behave unexpectedly
Provides Jest-based TypeScript testing expertise and best practices. Ensures proper test structure, mocking strategies, async handling patterns, and coverage optimization. Specializes in unit testing, integration testing, test organization with describe/it blocks, jest.mock patterns, snapshot testing, and testing library integration for UI components. Use when: writing TypeScript test files (.spec.ts, .test.ts), structuring tests with describe/it/test blocks, implementing mocks with jest.mock/jest.spyOn, testing async code with async/await or promises, creating test fixtures and helpers, implementing snapshot tests, testing React components with Testing Library, measuring and improving code coverage, or configuring Jest for TypeScript projects.