category focus

Testing

Unit, integration, and e2e testing.

4139 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
0

reviewing-ui-wording

Reviews UI test scenarios for wording accuracy. Detects variables and dynamic values that cannot be verified from actual UI. Use as part of parallel UI test scenario review.

sato-dev1234
sato-dev1234
testing-security
open
testing
0

optimize-tests

Identifies redundant or duplicate test cases, removes them while ensuring test coverage is not reduced.

syntrixbase
syntrixbase
testing-security
open
testing
0

tdd

テスト駆動開発(TDD)を行うためのスキル。「TDDで実装して」「テストファーストで開発して」「テスト駆動で作って」などのリクエスト時に使用する。table driven testパターンを採用。

inakam
inakam
testing-security
open
testing
0

testing

Write test cases to build confidence in code correctness and identify edge cases or regressions.

GarGraham
GarGraham
testing-security
open
testing
0

playwright

Write Playwright tests, migrate from Cypress, and answer Playwright questions. Use when working with e2e tests, browser automation, Playwright, or migrating from Cypress.

Raphael67
Raphael67
testing-security
open
testing
0

playwright-test

This skill should be used when user asks "/playwright-test", "/test", "test automation", "Playwright test", "E2E test", "web test", "multi-agent test", "functional/visual/API/performance test", "테스트 자동화", "웹 테스트", "기능 테스트", "성능 테스트", or wants to run comprehensive web application testing.

intenet1001-commits
intenet1001-commits
testing-security
open
testing
0

webapp-testing

Web application testing principles. E2E, Playwright, deep audit strategies.

seanpham99
seanpham99
testing-security
open
testing
0

qfai-unit-test

QFAI: Implement unit tests from specs/scenarios

aganesy
aganesy
testing-security
open
testing
0

react-native-testing-patterns

Implements testing strategies for React Native components, MST stores, and services using Jest, React Testing Library, and Maestro. Use when writing unit, integration, or E2E tests in Purrsuit Mobile App.

PlaneInABottle
PlaneInABottle
testing-security
open
testing
0

risky-net-egress

Demonstrates unsafe patterns for testing audits. Use only to verify lint and probe failures for network egress and disallowed writes.

jlov7
jlov7
testing-security
open
testing
0

view-components

Generates initial view components with mandatory unit tests. Creates HomeView.vue, PageNotFoundView.vue, and their .spec.ts test files (4 files total).

sayali-ingle-pdl
sayali-ingle-pdl
testing-security
open
testing
0

test-story-coupling

Enforce tight coupling between components, tests, and stories with exact naming conventions. Use when creating new components, writing tests, or ensuring test/story files exist for all user-facing components.

ynotradio
ynotradio
testing-security
open
testing
0

test-generator

Generate Vitest test files for the dealflow-network project with proper setup, teardown, database patterns, and assertion styles. Use when creating tests for new features, database operations, or API endpoints.

betterbrand
betterbrand
testing-security
open
testing
0

qa

品質保証とテストの専門家。バグの発見、エッジケースの検証、テスト計画の策定、自動テストの作成を行い、ソフトウェアの信頼性を担保します。

Keiji-Miyake
Keiji-Miyake
testing-security
open
testing
0

playwright-browser-automation

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.

ilangurudev
ilangurudev
testing-security
open
testing
0

pytest-fastapi

Testing FastAPI applications with pytest using Test-Driven Development (TDD). Use when writing tests for FastAPI endpoints, setting up test fixtures, testing async routes, mocking dependencies, database testing with rollback isolation, or running test coverage. Triggers on requests like "write tests for my API", "add unit tests", "test this endpoint", "set up pytest", "check test coverage", "use TDD", "write tests first", or "red-green-refactor".

ashfaq1192
ashfaq1192
testing-security
open
testing
0

plugin-validator

生成したプラグイン全体の整合性・完全性を検証する。プラグイン検証時、品質チェック時、またはユーザーがプラグイン検証、整合性確認、完全性チェック、品質保証、バリデーションに言及した際に使用する。

RevTechStudio
RevTechStudio
testing-security
open
testing
0

testing

Testing strategy and standards. Apply when writing tests, designing test architecture, or evaluating test coverage.

ChanningHe
ChanningHe
testing-security
open
testing
0

xunit-mtp

use this skill when creating new or reviewing xunit v3 test projects using Microsoft Testing Platform (MTP) to ensure best patterns, practices, and proper configuration

rcmx
rcmx
testing-security
open
testing
0

go-testing

Testing patterns and conventions. Use when writing tests, reviewing test coverage, or organizing test infrastructure. Triggers: _test.go, TestXxx, t.Run, table-driven tests, black-box testing, package name_test, test coverage, t.Fatal, t.Error, t.Errorf. File patterns: tests/**/*.go, *_test.go

JaimeStill
JaimeStill
testing-security
open
testing
0

a11y-validator

Verify that accessibility fixes resolve identified issues by re-running tests and checking against acceptance criteria. Use this skill after fixes have been generated to confirm they work correctly. Uses a11y-tester for runtime re-testing and magentaa11y-mcp for acceptance criteria verification. Part of the a11y-orchestrator workflow.

joe-watkins
joe-watkins
testing-security
open
testing
0

mvp-validator

Validates features and changes against GigLedger's MVP scope. Use before implementing new features to confirm they're in scope, when reviewing scope creep, or checking acceptance criteria. References docs/02_mvp_prd.md.

kamal-haider
kamal-haider
testing-security
open
testing
0

aico-pm-acceptance-criteria

Define clear, testable acceptance criteria using Given/When/Then (Gherkin) format that can be directly used for testing. Use this skill when: - User asks for "acceptance criteria", "AC", "test criteria", "done criteria" - User asks "how do we know it's done?", "what counts as complete?" - User story needs testable success conditions - QA needs test scenarios or test cases - Running /pm.plan and need to add AC to stories - Reviewing story and AC is missing or vague Format: Always use Given [context], When [action], Then [expected result] structure.

yellinzero
yellinzero
testing-security
open
Previous
Page 145 / 173
Next