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

tdd-red-green-refactor

Enforce TDD workflow (red → green → refactor). Use for any code change that is testable.

skillrecordings
skillrecordings
testing-security
open
testing
0

condition-based-waiting

Replace arbitrary timeouts with condition polling for reliable async tests

yousufjoyian
yousufjoyian
testing-security
open
testing
0

test-runner

Skill para ejecutar y gestionar tests. Incluye patrones de testing, fixtures comunes, y estrategias de debugging de tests fallidos.

Vasallo94
Vasallo94
testing-security
open
testing
0

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

JohnStrunk
JohnStrunk
testing-security
open
testing
0

testing-workflow

Write comprehensive tests following project conventions (tiers, patterns, anti-patterns). Use when writing tests, improving test coverage, fixing failing tests, or reviewing test quality.

Awannaphasch2016
Awannaphasch2016
testing-security
open
testing
0

write-test

테스트 코드를 작성할 때 이 정책을 따르세요.

GrowWeek
GrowWeek
testing-security
open
testing
0

nomos-test-execution

Orchestrates test execution for the Nomos monorepo following TESTING_GUIDE.md standards. Use this when running tests, debugging test failures, validating coverage, or executing verification checklists from AGENTS.md files.

autonomous-bits
autonomous-bits
testing-security
open
testing
0

tdd

Enforces test-driven development (TDD) following Kent Beck's methodology. MANDATORY micro-cycle approach - write ONE test, watch it fail, write minimal implementation, refactor, then NEXT test. NEVER write all tests first or implementation first. Use for ANY code writing task.

narcisobenigno
narcisobenigno
testing-security
open
testing
0

fixtures-generator

Generates valid and invalid JSON fixtures for CommandDTO and DecisionDTO based on current contract schemas.

Nepopams
Nepopams
testing-security
open
testing
0

adding-formal

Provides ASSERT/ASSUME macro pattern, .sby file template, and f_past_valid usage. Triggers when adding formal verification or writing assertions.

pbozeman
pbozeman
testing-security
open
testing
0

testing

単体テストルール。フラット構造、モック使用制限、パラメータ化テスト、テストピラミッドなどの規約を定義。Vitest/Jest使用時に参照。

DIO0550
DIO0550
testing-security
open
testing
0

msw

Mocks APIs with Mock Service Worker including request handlers, server/browser setup, and testing integration. Use when mocking APIs in tests, developing without backend, or simulating network conditions.

mgd34msu
mgd34msu
testing-security
open
testing
0

mock-infrastructure-engineer

Creates and optimizes MSW (Mock Service Worker) handlers for Playwright E2E tests, implementing handler caching, fixture management, and AI Gateway mocking patterns. Use when mock setup is slow or test data needs centralization.

d-oit
d-oit
testing-security
open
testing
0

tdd-workflow

TDD(テスト駆動開発)のワークフローをガイドする。 Red → Green → Refactor のサイクルに従って開発を進める。 「TDDで実装」「テスト駆動」などのキーワードで自動適用。

hironow
hironow
testing-security
open
testing
0

verify-ui-changes

Standard procedure for verifying UI updates and bug fixes using the browser subagent.

canyouseeus
canyouseeus
testing-security
open
testing
0

code-test

Enforce test-driven development (RED-GREEN-REFACTOR). Use when implementing features, fixing bugs, or changing behavior - write failing test first, then minimal code to pass.

srnnkls
srnnkls
testing-security
open
testing
0

tdd

Use when implementing any feature or bugfix - write test first, watch it fail, then implement

TKontu
TKontu
testing-security
open
testing
0

tech-spike

技術検証(Tech Spike)ワークフロー。ライブラリ選定やアーキテクチャ判断の前に最小限の実験コードで技術的妥当性を検証。 使用タイミング: (1) 複数の技術選択肢がある場合(ライブラリA vs B) (2) 新しいライブラリ・技術の学習コストが高い場合 (3) パフォーマンス・互換性の懸念がある場合 (4) 既存システムとの統合リスクがある場合 (5) 「技術検証」「ライブラリ調査」「スパイク」リクエスト 使用しない場合: 技術スタック確定済み、既知のパターン、単純なCRUD操作

hyt-sasaki
hyt-sasaki
testing-security
open
testing
0

unit-testing

Unit testing patterns for .NET applications using EF Core In-Memory Provider, AAA structure, test data helpers, and TDD workflows. Use when writing unit tests for Application Services, domain logic, or data access.

michaellperry
michaellperry
testing-security
open
testing
0

api-contract-validator

Validates API contracts for correctness, compatibility, and compliance. Tests REST APIs against OpenAPI/Swagger specifications. Detects breaking changes between versions, validates runtime responses against schemas, and ensures backward compatibility before deployment.

chaserbreitenbach
chaserbreitenbach
testing-security
open
testing
0

flow-convert-activities-to-steps

Convert Flow SDK activities.ts to Output SDK steps.ts. Use when migrating activity functions to step definitions with typed parameters.

growthxai
growthxai
testing-security
open
testing
0

mocking-strategies

Test mocking strategies with Vitest. Use when mocking dependencies in tests.

IvanTorresEdge
IvanTorresEdge
testing-security
open
testing
0

app-testing

Guide for writing frontend tests including unit tests with Vitest, component tests, and visual/E2E tests with Playwright MCP. Use when creating tests for hooks, components, or pages.

dairectiv
dairectiv
testing-security
open
Previous
Page 168 / 173
Next