e2e-testing
E2Eテストの作成・デバッグ・失敗修正を支援。Playwrightテスト失敗時、新規テスト作成時、テストメンテナンス時に使用。Use when "test failed", "flaky test", "E2Eが落ちた", "テストが動かない", "Playwright error" と言われた時。
E2Eテストの作成・デバッグ・失敗修正を支援。Playwrightテスト失敗時、新規テスト作成時、テストメンテナンス時に使用。Use when "test failed", "flaky test", "E2Eが落ちた", "テストが動かない", "Playwright error" と言われた時。
Automated unit test generation for new functionalities using Jest. This skill ensures that every new controller, service, or repository has corresponding unit tests following the project's mocking and structure patterns.
Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic.
Backend testing with pytest including fixtures, mocking, async tests, and database testing. Use for FastAPI/Python test implementation.
This skill should be used when the user asks to "verify test quality", "run mutation testing", "prove tests catch bugs", "check test effectiveness", or automatically after the TDD cycle completes in task-executor. Mutation testing proves that your tests actually catch bugs by introducing deliberate mutations and verifying tests fail.
Test automation, manual testing ve quality assurance için kullanılır. Jest, Playwright, test coverage ve accessibility testing konularında uzman.
XCTest/XCUITestを用いたiOSアプリのテスト設計支援スキル。テスト戦略立案、モック/スタブ設計、テストデータ管理、カバレッジ分析を包括的にサポート。Use when: iOSテスト設計、XCTest実装、UITest作成、テストカバレッジ向上、テスト戦略立案、テストダブル設計。
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. NOTE - Prefer Playwright MCP for direct browser control when available.
Generate comprehensive tests with edge cases, mocks, and proper coverage. Use when asked to write or improve tests.
Visual verification and browser automation using Playwright
Go testing conventions and patterns. Use when writing tests, discussing coverage, or editing _test.go files. Triggers: test organization, black-box testing, table-driven tests, HTTP mocking, coverage criteria, test naming, dependency skipping.
Generates comprehensive UI test scenarios with template-based quality check. Use when user requests UI test scenarios, manual test cases, or end-to-end test documentation.
嚴格測試協議。強制執行「如果沒測試,就不算完成」原則。 觸發時機: - 修復 bug 時(必須新增回歸測試) - 實作新功能時(必須有對應測試) - 修改現有代碼時(確保測試仍通過) - 用戶提到「測試」、「test」、「驗證功能」
Generates comprehensive unit tests for code. Detects the testing framework, creates tests with edge cases and mocks, and follows best practices. Use when the user wants to generate tests for their code or needs test coverage.
Launch Leavn app in iOS simulator, navigate features using MCP browser tools, take screenshots, verify UI rendering and feature functionality
Add or debug neovim plugins with lazy.nvim, including e2e testing via remote API
Test-Driven Development patterns for FastAPI with pytest
Review test coverage quality and completeness. Use after creating a PR or adding new functionality to ensure tests adequately cover new code and edge cases.
Use when writing tests for TypeScript or JavaScript code in frameworks such as Jest, Vitest, Bun, etc.
Guidelines for writing unit and integration tests, including mocking strategies and coverage goals.
Build a TDD-ready Starknet/Cairo repo from a detailed protocol spec using progressive disclosure. Use when asked to transform a deep spec into interface/abstract skeletons, test infrastructure, BTT trees, and placeholder tests, with strict coverage validation and no business-logic implementation.
Playwright end-to-end testing patterns including page object models, test scenarios, visual regression, and CI/CD integration. Use when building E2E tests, testing web applications, automating browser interactions, implementing page objects, running Playwright tests, debugging E2E failures, or when user mentions Playwright, E2E, browser automation, page object model, POM, visual regression, or end-to-end testing.