Results for “test”

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Sets up Microsoft Testing Platform hot reload to iterate fixes on failing tests without rebuilding, covering package installation, environment configuration, and the iterative workflow.

Runs adversarial UI tests in a real browser, covering functional, accessibility, responsive, and UX checks, with diff-driven, exploratory, and parallel workflows.

Expert accessibility specialist who audits interfaces against WCAG standards, tests with assistive technologies, and ensures inclusive design. Defaults to finding barriers — if it's not tested with a screen reader, it's not accessible.

Write, review, or refactor C# unit tests using XUnit v3, NSubstitute, FluentAssertions, and Atc.Test. Use this skill whenever the user asks to create tests, add test coverage, fix failing tests, mock dependencies with NSubstitute, or follow the ClassName_MethodUnderTest_ExpectedBehavior naming convention in a .NET/C# project.

Use when writing or reviewing tests, or when asked how to write a good single test. Encodes the per-test rules behind the "test the contract / responsibility, not the implementation" principle — name and structure one behavior per `it`, drive through the public surface, stub only true external boundaries, control time and config via documented knobs, and keep tests clear, isolated, and refactor-resilient. The same rules drive both authoring (write mode) and auditing existing tests (review mode).

Testing and debugging for Zephyr RTOS. Covers the Ztest framework for unit and integration tests, the Twister test runner for automated HIL/SIM validation, and advanced tracing/debugging techniques (SystemView, Thread Analyzer, Stack analysis). Trigger when writing unit tests, setting up CI/CD pipelines, or analyzing system performance and latency.

Extracts a language-agnostic ghost package (spec, tests, install and verify docs) from an existing repository, preserving behavior via tests.yaml and evidence bundles.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Use when writing or modifying tests for Ink (terminal UI) components.

Get best practices for NUnit unit testing, including data-driven tests

Get best practices for TUnit unit testing, including data-driven tests

Get best practices for XUnit unit testing, including data-driven tests

Use this skill when managing post-SAP follow-up testing for a driver. Covers the testing cadence, recordkeeping, what happens if a test is missed, and how to transition the schedule to a new employer.

Expert knowledge for Azure Test Plans development including limits & quotas, security, and integrations & coding patterns. Use when configuring test run custom fields, data retention, permissions, access levels, or tcm.exe automation, and other Azure Test Plans related development tasks. Not for Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Azure App Testing (use azure-app-testing), Azure Boards (use azure-boards).

Tests local web applications with Playwright, including server lifecycle management, DOM inspection, and screenshot capture.

Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

`analysis-agent`/`task-agent`/`review-agent`: use when logic, rules, invariants, branches, edges, or failure paths need isolated tests; skip without a unit-test decision.

Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

Get best practices for JUnit 5 unit testing, including data-driven tests

Skill for the Tests area of paddock. 44 symbols across 6 files.

Automated test validation, coverage checking, and quality metrics with aggressive defaults

Line coverage answers "did this line execute during the test run".

Tests React Native applications E2E with Detox, gray box testing, and device synchronization.

Exploratory ("monkey") QA of a live app as GUEST then LOGGED-IN, then diff. Headed playwright-cli, junk inputs, nav abuse. Use when "monkey test the app", "exploratory QA", "wander like a confused user", or "guest vs logged in". Story CRUD → test-qa. Hostile sweep → test-red-team. This-diff PDCA → test-playwright.

Recommends confirmatory testing with corticotropin stimulation test in patients presenting with clinical symptoms or signs suggesting PAI (e.g., fatigue, hypotension, hyponatremia, hyperpigmentation) when the patient's condition permits safe testing. Use when a clinician identifies suggestive features and circumstances allow outpatient stimulation testing without imminent need for emergency glucocorticoids.

Configures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs.

Write and run test-driven Laravel applications using PHPUnit, Pest, factories, HTTP tests, and Sanctum authentication.

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

`analysis-agent`/`task-agent`/`review-agent`: use to recommend a risk-to-test evidence portfolio and omissions; skip test implementation, fixed-command, and release-verdict work.

`analysis-agent`/`task-agent`/`review-agent`: use when fixtures, factories, seeds, isolation, cleanup, or sensitive test-data rules change; skip when test data is unaffected.