Results for “test”

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

A B Testing Based Design Skill

使用Test2::V0、Test::More、prove runner、模拟、Devel::Cover覆盖率和TDD方法的Perl测试模式。

pytest Python testing framework. Covers fixtures, parametrize, and mocking. Use for Python testing. USE WHEN: user mentions "pytest", "python test", "fixture", asks about "@pytest.fixture", "@pytest.mark.parametrize", "conftest.py", "pytest coverage", "python unit test" DO NOT USE FOR: JavaScript/TypeScript - use `vitest` or `jest`; Java - use `junit`; E2E web tests - use `playwright`; Load testing - use locust

Provides file paths to language-specific reference files for polyglot test analysis skills, enabling framework-aware detection of test markers, assertions, and patterns across .NET, Python, TypeScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++.

Grades individual test methods and produces a compact markdown table with a letter grade, score band, and one-line note for each test.

Analyzes .NET test suites for duplicated boilerplate, copy-paste tests, and structural maintainability issues, producing a report with concrete before/after refactoring suggestions.

Runs a hypothesis-driven debugging workflow that reproduces failures, forms discriminating tests, proves root cause via toggle, and delivers a fix, regression test, and postmortem.

Guides test-driven development for Spring Boot services with JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo, covering unit, web, integration, and persistence tests.

Runs load, stress, and performance tests using k6, JMeter, and profiling tools, with capacity planning and benchmarking for APIs and backend services.

Designs and executes load tests, covering scenario design, baseline capture, execution configuration, results analysis, and reporting for k6, Locust, Gatling, and JMeter.

Expert technology assessment specialist focused on evaluating, testing, and recommending tools, software, and platforms for business use and productivity optimization

Guides end-to-end testing of frontend applications using Playwright or Cypress, covering multi-page user flows in real browsers, API mocking, and CI integration.

Use when writing or modifying tests in a Bun project

Write a focused test plan that scopes what will be tested, ranks risks, enumerates cases, and sets explicit entry and exit criteria.

Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"

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.

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.

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

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.

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".

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".

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".

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.