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

write-tests

Generates comprehensive unit tests and integration tests for code with test coverage analysis and edge cases

ltoscano
ltoscano
testing-security
open
testing
0

kratos-tests

Generates comprehensive table-driven tests for go-kratos microservices using testify/mock and testify/assert. Creates repository tests with in-memory SQLite, business layer tests with mocks, and service layer tests with proper context propagation. Use when writing unit tests for any kratos layer, adding test coverage, creating mock implementations, or validating CRUD operations.

alecszaharia
alecszaharia
testing-security
open
testing
0

verify-spec-compliance

Terraformコードの整合性と内部一貫性を検証します。ユーザーがコードの品質チェックやレビューを求めた場合に使用してください。

t-taketake
t-taketake
testing-security
open
testing
0

testing-patterns

Testing patterns with Vitest, React Testing Library, and Playwright. Use when writing unit tests, component tests, integration tests, or end-to-end tests for React/Next.js applications.

Naw3
Naw3
testing-security
open
testing
0

qa-validation

Validate implementation against test cases and acceptance criteria. Use when checking if code works correctly, validating against user-provided test cases, or verifying acceptance criteria are met. Gets test cases from user input or previous workflow stages.

shvee-pandora
shvee-pandora
testing-security
open
testing
0

main-process-unit-tests

This document describes how to write unit tests for the Electron main process (`src/main`). Use this when asked to create or update and fix unit tests.

trae-op
trae-op
testing-security
open
testing
0

testing

Use when writing or modifying tests, fixing bugs with TDD, reviewing test code, or when user mentions "test", "tests", "testing", "TDD", "test-driven", "pytest", "add tests", "write tests", "unit test", "integration test", "test coverage", "bug fix", "fix bug", "verify", "edge case", "mocking", "patch.object".

gigaverse-app
gigaverse-app
testing-security
open
testing
0

python-best-practices

Type hints, dataclasses, async patterns, testing with pytest, and modern Python tooling

nategarelik
nategarelik
testing-security
open
testing
0

juju

Develop and test against a real Juju controller

tonyandrewmeyer
tonyandrewmeyer
testing-security
open
testing
0

rspec-testing

Write and update RSpec tests following BDD principles with behavior-first approach, characteristic-based context hierarchy, and happy path priority. **Activate when:** user mentions RSpec/specs/testing, works with *_spec.rb files, asks to write/add/update/fix tests, or requests test coverage. Ensures tests describe observable behavior, not implementation details.

AlexeyMatskevich
AlexeyMatskevich
testing-security
open
testing
0

testing-strategies

Build confidence with comprehensive CLI testing. Unit tests catch logic bugs with fakes, integration tests verify API contracts, E2E tests validate workflows.

adaptive-enforcement-lab
adaptive-enforcement-lab
testing-security
open
testing
0

testing

Policies for unit testing, E2E testing, and test-running constraints for DBConvert Streams UI.

slotix
slotix
testing-security
open
testing
0

tdd-implementation

container-use環境内でのTDD実装フロー(Red→Green→Refactor)、テスト項目書の活用、DBマイグレーションテストを定義

takemo101
takemo101
testing-security
open
testing
0

check-test-coverage

Standard procedure for checking test coverage using pytest-cov in the airline-discount-ml project.

ei-stanko-zdravkovic
ei-stanko-zdravkovic
testing-security
open
testing
0

sync-test-binary

Update test binaries (test_stream_generator.rs) to match the latest architecture from main.rs, ensuring they use the same caching, rendering, and pagination patterns. Use when test binaries need to be synchronized with production code.

tercen
tercen
testing-security
open
testing
0

qa-behavioral-tester

Executes behavioral API tests by spinning up the service and making real HTTP requests. Validates status codes, response structure, and data correctness.

pcortes
pcortes
testing-security
open
testing
0

minitest

This skill should be used when the user asks about "Minitest", "Rails testing", "test/", "fixtures", "ActiveSupport::TestCase", "ActionDispatch::IntegrationTest", "system tests", "functional tests", "assert", "assert_equal", "assert_difference", "test_helper", "rails test", or needs guidance on testing Rails applications with the default Minitest framework.

bastos
bastos
testing-security
open
testing
0

tdd-workflow

TDDワークフローを強制し、テストファースト開発を支援します。新機能実装時に自動起動し、Red-Green-Refactorサイクルを確実に実行します。

drillan
drillan
testing-security
open
testing
0

verification-before-completion

Use when about to claim work is complete, fixed, passing, or done - requires running verification commands and confirming output before making any success claims. Evidence before assertions.

gvarela
gvarela
testing-security
open
testing
0

tdd-cycle

Execute a complete TDD cycle (RED → GREEN → REFACTOR) for one test. Orchestrates the full workflow from writing a failing test through implementation and refactoring to commit.

SwiftyJunnos
SwiftyJunnos
testing-security
open
testing
0

feature-verifier

Analyze test failures and suggest fixes for Feature Swarm verification. Use when tests fail during the verification phase to diagnose root cause and determine if automatic recovery is possible.

pcortes
pcortes
testing-security
open
testing
0

task-dispatch

Subagent-driven task execution with TDD workflow. Dispatches tester subagent (writes failing tests) then implementer subagent (makes tests pass), with batch review.

srnnkls
srnnkls
testing-security
open
testing
0

unit-test-generator

Generate pytest unit tests for Python functions and classes with fixtures, parametrization, and edge cases. This skill should be used when creating test coverage for modules, especially during refactoring to ensure functionality is preserved.

omriwen
omriwen
testing-security
open
testing
0

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 coverage, (4) The test suite failed to catch a production issue. Forces a conversation about what user experience we're protecting before writing any test code.

ajmartin94
ajmartin94
testing-security
open
Previous
Page 130 / 173
Next