category focus

Testing

Unit, integration, and e2e testing.

4139 مهارةall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
453

test-environment

Test environment system (DomeGradient, IBLGradient, default lighting, component schemas) against the poke example using the iwsdk CLI.

facebook
facebook
testing-security
open
testing
453

test-interactions

Test XR interactions (ray, poke/touch, dual-mode, audio, UI panel) against the poke example using the iwsdk CLI.

facebook
facebook
testing-security
open
testing
452

gen-rtl-test

Generate React Testing Library tests following OCP Console best practices

openshift
openshift
testing-security
open
testing
452

test

Run tests (frontend, backend, unit, or all)

openshift
openshift
testing-security
open
testing
449

git-bisect

Find the commit that introduced test failures using git bisect

ag-grid
ag-grid
testing-security
open
testing
448

elevenlabs-model-update

ElevenLabs の新モデル追加時に使用。provider2agent.ts のモデルリスト更新とテストスクリプト更新を行う。

receptron
receptron
testing-security
open
testing
446

bunit-test-migration

Migrate bUnit test files from deprecated beta API (1.0.0-beta-10) to bUnit 2.x stable API. Use this when working on .razor test files in BlazorWebFormsComponents.Test that contain old patterns like TestComponentBase, Fixture, or SnapshotTest.

FritzAndFriends
FritzAndFriends
testing-security
open
testing
446

contoso-migration-test

**WORKFLOW SKILL** — Execute end-to-end ContosoUniversity migration benchmark: clear output folder, run L1 script + L2 Copilot transforms, build, run Playwright acceptance tests, and generate a numbered run report. WHEN: "run contoso migration test", "test contoso university migration", "contoso migration benchmark", "run CU migration". INVOKES: bwfc-migrate.ps1, bwfc-migration skill, bwfc-data-migration skill, bwfc-identity-migration skill, migration-standards skill, dotnet CLI, Playwright tests.

FritzAndFriends
FritzAndFriends
testing-security
open
testing
443

testing

Testing workflow for the rstest monorepo. Use when running tests, writing test files, debugging test failures, or validating changes.

web-infra-dev
web-infra-dev
testing-security
open
testing
442

run-tests

Run dojo tests, analyze failures, and debug issues. Use when testing code changes, running pytest, verifying fixes, or debugging test failures.

pwncollege
pwncollege
testing-security
open
testing
441

dd-tf-provider-test-runner-agent

Run Datadog Terraform provider acceptance tests with proper RECORD modes and capture output for analysis. This agent is invoked via Task tool and writes results to files.

DataDog
DataDog
testing-security
open
testing
441

fix-broken-integration-tests

End-to-end workflow to diagnose, reproduce, fix, and validate a failing Datadog Terraform provider integration test. Takes any input pointing at specific tests: test function names, error messages, resource names, or any other description of what's failing. Runs autonomously through 8 phases — identify → validate in CI → reproduce locally → plan fix → execute → open draft PR → monitor → report.

DataDog
DataDog
testing-security
open
testing
435

doc-testing

Comprehensive guide for writing tests in magenta.nvim, including test environment setup, mock providers, driver interactions, and best practices

dlants
dlants
testing-security
open
testing
434

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

corvo007
corvo007
testing-security
open
testing
434

power-query

Author, validate, and test Power Query M expressions in semantic model partitions. Automatically invoke when the user mentions "Power Query", "M code", "M expression", "partition expression", "query folding", or asks to "write Power Query", "fix Power Query", "test a partition", "preview partition data", "debug Power Query step", "optimize Power Query".

data-goblin
data-goblin
testing-security
open
testing
432

unit-test-implementation

Best practices for implementing unit tests in this TypeScript monorepo. Use when writing new tests, refactoring existing tests, or fixing failing tests. Covers mocking strategies, test organization, helper functions, and assertion patterns.

AztecProtocol
AztecProtocol
testing-security
open
testing
432

acir-formal-proofs

Build and run ACIR formal proof tests with SMT verification. Generates ACIR artifacts from noir's ssa_verification tool, then runs each test individually with user-specified time/memory limits, and updates the README results table.

AztecProtocol
AztecProtocol
testing-security
open
testing
432

debug-e2e

Interactive debugging for failed e2e tests. Orchestrates the debugging session but delegates log reading to subagents to keep the main conversation clean. Use for ping-pong debugging sessions where you want to form and test hypotheses together with the user.

AztecProtocol
AztecProtocol
testing-security
open
testing
432

ci-maintenance-workflow

CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user asks you to run the "Write a PR For A Failing Test", "Fix A Failing Smoke Test", "Mark Slow Tests", or "Review PR According to Agent-Checkable Standards" workflow.

UKGovernmentBEIS
UKGovernmentBEIS
testing-security
open
testing
432

ensure-test-coverage

Ensure test coverage for a single evaluation - both reviewing existing tests and creating missing ones. Analyzes testable components, checks tests against repository conventions, reports coverage gaps, and creates or improves tests. Use when user asks to check/review/create/add/ensure tests for an eval. Use whenever you are asked to review an evaluation that contains tests, or whenever you need to write a suite of tests. Do NOT use for fixing a specific failing CI test (use ci-maintenance-workflow instead).

UKGovernmentBEIS
UKGovernmentBEIS
testing-security
open
testing
431

feature-spec

Write browser-based Capybara feature specs for WikiEduDashboard controllers and views. Use this skill when asked to improve test coverage, write feature specs, add browser tests, or cover a controller with specs.

WikiEducationFoundation
WikiEducationFoundation
testing-security
open
testing
430

electrobun-kitchen-sink

Use when working with the Electrobun Kitchen Sink testing app — running tests, understanding the feature manifest, navigating the test runner UI, operating playground windows, or adding new test coverage. Also activates for questions about the defineTest() pattern, AUTO_RUN mode, or the manifest generator/validator scripts.

milady-ai
milady-ai
testing-security
open
testing
430

electrobun-testing

Use when writing Electrobun tests, adding test coverage to the Kitchen Sink, implementing the defineTest() pattern, generating new test suites, understanding what the kitchen sink tests, or reverse-engineering component behaviour from test source. Activates on test authoring, test framework, or test-driven development questions.

milady-ai
milady-ai
testing-security
open
testing
425

nuxt-test-utils-skilld

ALWAYS use when writing code importing "@nuxt/test-utils". Consult for debugging, best practices, or modifying @nuxt/test-utils, nuxt/test-utils, nuxt test-utils, nuxt test utils, test-utils, test utils.

nuxt-modules
nuxt-modules
testing-security
open
Previous
Page 51 / 173
Next