backend-testing
Write tests for backend services, APIs, and database access. Use when testing Express/Fastify handlers, services with database calls, or integration tests.
Write tests for backend services, APIs, and database access. Use when testing Express/Fastify handlers, services with database calls, or integration tests.
Use this when running or adding tests (compile/lint/unit/E2E), updating test utilities, or working with Playwright/visual testing in markdowntown.
Generates comprehensive test files for functions and classes. Use after writing a function, method, or class to quickly create unit tests with edge cases, assertions, and proper test structure. Supports multiple testing frameworks (pytest, unittest, jest, etc.) and follows testing best practices (AAA pattern, mocking, fixtures).
Generate Playwright configuration files for cross-browser E2E testing. Triggers on "create playwright config", "generate playwright configuration", "playwright setup", "browser testing config".
Эксперт Android тестирования. Используй для JUnit, Espresso и Android test patterns.
Lightweight reference for designing meaningful test variations.
RED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior.
Run and extend the end-to-end HTTP integration tests (SQLite in-memory) for mjr.wtf, covering auth, create/list/delete, redirects, and analytics. Use when changing handlers, middleware, or API contracts.
检查Given-When-Then格式规范性,发现场景缺口,提供丰富建议。当BDD场景编写完成后使用,确保场景质量符合CRAFT标准。
How tests should be structured, named, and prioritized in this codebase.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Fix HTTP client misuse in Output SDK steps. Use when seeing untraced requests, missing error details, axios-related errors, or when HTTP calls aren't being properly logged and retried.
Enforces Test-Driven Development workflow with automated test-first validation. Use when implementing features, fixing bugs, running @Coder workflow, or when the user mentions TDD, testing, red-green-refactor, or verification gates. Ensures tests are written BEFORE implementation code.
Migrate from Vitest 2.x/3.x to 4.x with pool options, coverage config, workspace to projects, and browser mode updates. Use when upgrading Vitest versions or encountering deprecated patterns.
Playwright best practices including selectors, wait strategies, accessibility testing, responsive design, and flaky-test prevention. Use when writing or improving Playwright E2E tests.
Use when implementing an APPROVED OpenSpec change. Read tasks.md and follow EXACTLY. Do not deviate, add features, or skip tasks. Use with test-tdd for each code task.
Generate RSpec test files for Ruby on Rails code. Creates model specs, request specs, service specs, and other test types. Uses FactoryBot when available in the project. Use when asked to write tests, create specs, add test coverage, or generate RSpec files.
End-to-end browser testing patterns with Playwright. Use when writing integration tests, user flow testing, or browser automation.
Write comprehensive tests (unit, integration, e2e), manage test coverage, and ensure code quality. Use when writing tests, improving coverage, or debugging test failures.
Write Pest PHP feature tests following RentPath conventions. Use for writing new tests, understanding test patterns, using factories, and ensuring proper coverage. Auto-triggers on "write test", "add test", "test this feature", "create test", "test coverage".
Run and debug Rust tests for glhf. Use when running tests, fixing test failures, or adding new test cases.
Use when designing or refactoring automated tests to make them high-signal, reliable, and maintainable across unit, integration, and end-to-end suites.
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Test game via browser with Chrome DevTools. Navigate UI, play through game flow, observe behavior and report issues.