GitHub
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Skills IA documentation testing
Découvrez les skills documentation testing, comparez leurs dépôts et consultez leurs instructions.
Catégories: documentation testing
documentation testing Effacer les filtres
Explorer
GitHub
backend-testing
執行與除錯 KCardSwap 後端測試（pytest）：支援快速跑全套、只跑 unit/integration、單一檔案或單一測試、失敗重跑、最慢測試統計、coverage 報告，以及 gcs_smoke（RUN_GCS_SMOKE=1）等情境。也包含本機 Poetry 與 Makefile...
GitHub
tdd
Use when implementing any feature or bugfix - write test first, watch it fail, then implement
GitHub
test-review
Analyze test coverage requirements and assess whether code meets testing standards. Use when reviewing test plans, evaluating test coverage, or assessing testing quality.
GitHub
ui-check-framework
Build or extend an extensible UI self-check framework for Web UIs (React/Vite or plain HTML) using Playwright. Use when asked to add/upgrade ui-check or ui-watch flows, enforce data-qa/data-testid discovery, ad...
GitHub
test-triage
Debugs failing tests, flaky tests, and Node processes that won't exit after tests complete. Use when backend/shared/frontend tests fail or hang.
GitHub
agent-browser
Browser automation and visual testing using agent-browser CLI. Use this skill for E2E testing, taking screenshots, interacting with web pages, and visual regression testing.
GitHub
watchos-testing
watchOS and iOS testing expert for unit tests, UI tests, and test-driven development. Use when working with XCTest, testing SwiftUI views, testing WatchKit components, or implementing test strategies for watch...
GitHub
phpunit-testing
Write PHPUnit tests for WordPress components following SOMA testing standards and conventions
GitHub
test-planning
Plan and design tests with a UX-first approach. Use this skill when: (1) Adding new features that need test coverage, (2) Fixing bugs and need to prevent regression, (3) Reviewing or improving existing test cov...
GitHub
dotnet-test-triage
Run dotnet test, capture failed test cases, and generate a rerun filter plus a markdown failure summary. Use when test runs fail and you need a focused rerun command or a compact failure report.
GitHub
phoenix-truth-case-orchestrator
End-to-end truth-case orchestration for the Phoenix VC fund-modeling platform. Use when running tests/truth-cases/runner.test.ts, computing module-level pass rates, updating docs/phase0-validation-report.md and...
GitHub
playwright-browser
Use when automating browsers, testing pages, or taking screenshots
GitHub
e2e-writer
Write E2E tests with Playwright using selector best practices. Use when you need to write end-to-end integration tests, user scenarios, or complete workflows.
GitHub
test-writer
Write unit and integration tests following AAA structure. Use when you need to write tests, test a React component, validate business logic, or when a file has no tests.
GitHub
mini-app-test
ミニアプリのテストを実施する。「テスト」「動作確認」「検証」を依頼されたときに使用する。
GitHub
unit-test
単体テストの作成。「テストを書きたい」「ユニットテストを追加」「関数をテスト」などのリクエスト時に使用。
GitHub
core-browser-automation
General-purpose patterns for reliable browser automation (selectors, waiting, scrolling, overlays, HITL).
GitHub
optimize-tests
Identifies redundant or duplicate test cases, removes them while ensuring test coverage is not reduced.
GitHub
skyline-tester
Use this skill when working with SkylineTester or the test list file.
GitHub
skyline-nightlytests
Use this skill when looking at nightly test results or investigating test failures.
GitHub
integration-tests
Use this skill when writing or running integration tests. Provides approved model names and integration test guidelines.
GitHub
qa-tester
AI Quality Assurance Specialist for Test Planning, Test Cases, and Bug Reporting. Strictly follows project docs. Covers Unit, E2E, Security, Performance.
GitHub
test-driven-development
機能実装やバグ修正時に使用。RED-GREEN-REFACTORサイクルとTesting Trophy手法を強制。
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.