concurrent-testing-methodologies
Develop rigorous testing methodologies that capture concurrency-related defects and regressions.
Develop rigorous testing methodologies that capture concurrency-related defects and regressions.
Local Python-based browser automation toolkit using Playwright. Provides command-line tools for navigating, interacting with, and testing web applications without using MCP protocols. Supports clicking, typing, hovering, screenshots, content extraction, and JavaScript execution.
Integration testing patterns for ABP Framework APIs using xUnit and WebApplicationFactory. Use when: (1) testing API endpoints end-to-end, (2) verifying HTTP status codes and responses, (3) testing authorization, (4) database integration tests.
Use after writing a new skill and/or when testing existing skills, creating skill evaluations, or verifying skills work under pressure - applies TDD/RED-GREEN-REFACTOR to skill documentation by running baseline tests, measuring compliance, and closing rationalization loopholes
Write browser tests for end-to-end user workflows and JavaScript interactions using Pest v4 with Playwright. Use MINIMALLY - only for core areas, happy paths, and functionality that CANNOT be tested with feature tests. Browser tests replace QA smoke testing, not feature tests.
Write tests for Zod schemas. Use when testing entity schemas, DTO validation, query parameter schemas, or any schema validation rules. Triggers on "test schema", "schema tests", "test validation", "test zod".
Write failing unit tests for feature requirements (TDD style)
Writes unit tests for JavaScript/TypeScript and frontend projects using Vitest or Jest. Use when writing or running tests.
테스트 코드 작성 및 실행. Use when (1) "테스트 작성해줘", (2) "테스트 실행해줘", (3) 테스트 커버리지 확인. ⚠️ QA 테스트 요청은 별도 스킬 사용: - Slack 알림 전송 → request-test
Use when adding test pseudocode to user stories or implementation guides - creates MEDIUM-IMPLEMENTATION abstraction showing test structure with Vitest terminology, placeholder comments for logic, and strategic comments (Research/Fixture/Integration/Verification/Pattern/Decision) that guide what to research and decide, not complete implementations
Use Playwright to open a LiveLib quote page and add it to your own quotes/list via the website UI.
Enforce TDD workflow and ensure proper execution of the Red-Green-Refactor cycle. Use when starting a new feature implementation, bug fix, or refactoring.
Scaffolds pytest unit tests for Python backend functions and classes. Use when creating tests for FastAPI endpoints, services, and utilities.
Use when capturing screenshots, automating browser interactions, or scraping web content. Covers Playwright Python API for page navigation, screenshots, element selection, form filling, and waiting strategies.
实现任何功能或修复 bug 时使用,在编写实现代码之前先写测试。Use when implementing any feature or bugfix - write the test first, watch it fail, write minimal code to pass. TDD 红绿重构循环。
Use this when adding/fixing UI or smoke tests; prefer targeted Vitest runs first, then widen.
Test and validate API contracts against specifications
Test the SSE events router and real-time event streaming. Use when testing Server-Sent Events endpoint or event authorization. Triggers on "test events", "test sse", "test events router", "test real-time".
Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.
Workflow for propagating penguiflow library changes to test agents. Use when modifying library code and need to test changes in test_generation agents.
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices
Implements comprehensive testing across all quality dimensions - accuracy, performance, security, and accessibility. Use when building test strategies or ensuring production-grade quality assurance.
Run the app locally and take screenshots using Puppeteer to verify UI changes; use when validating demo pages, checking visual regressions, or capturing UI state for analysis
You are an implementer of unit and integration tests.