Results for “test”

Comprehensive LLM security testing prompts for bias detection, data leakage, alignment testing, and adversarial prompt resistance.

Laravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage.

Laravel testing strategies with PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage.

Design and evaluate paid-ad experiments with hypotheses, randomization, sample-size calculations, guardrails, and decision rules for A/B and split tests.

Generates comprehensive unit tests with edge cases, error paths, and boundary values. Auto-detects the test framework, scans for untested functions, adopts existing conventions, runs tests, and self-heals failures in up to 3 iterations while measuring coverage.

Provides expert guidance for testing Spring Boot 4 applications with modern patterns, test slices, and best practices.

Create comprehensive accessibility testing plans covering automated tools, manual testing, assistive technologies, and WCAG criteria.

Generates unit tests for code changed in the current branch by comparing against origin/main and following existing test conventions.

Manage Kind (Kubernetes in Docker) clusters for local development and testing, including cluster creation, platform deployment, and E2E test workflows.

Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.

Kotest — flexible, idiomatic Kotlin testing framework. Multiple specification styles (StringSpec, FunSpec, BehaviorSpec, DescribeSpec, FeatureSpec, FreeSpec), rich matcher library, property-based testing, data-driven tests, coroutine support, KMP-friendly. Drop-in alternative or complement to JUnit. USE WHEN: user mentions "Kotest", "io.kotest", "shouldBe", "StringSpec", "BehaviorSpec", "DescribeSpec", "kotest property testing", "Arb.list", "forAll", "kotest matchers", "kotlin tests" DO NOT USE FOR: JUnit-specific patterns - use junit skill (or framework-specific test skills) DO NOT USE FOR: Flow testing - use `testing/turbine` DO NOT USE FOR: Compose snapshot tests - use `testing/compose-snapshot` DO NOT USE FOR: Mobile E2E - use `testing/maestro`

Expert knowledge for Azure App Testing development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when running Azure Load Testing, Playwright Workspaces, JMeter/Locust tests, VNet/private endpoint tests, or CI/CD test pipelines, and other Azure App Testing related development tasks. Not for Azure Test Plans (use azure-test-plans), Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Playwright Workspaces (use azure-playwright-workspaces).

API Test Suite Builder

Composite skill — diagnose, repair, and validate a test suite end-to-end. Chains test-health (diagnose) → config-drift-detect (gate compatibility) → test-cleanup (prune + add integration tests) → mutation-test (validate survivors) → adr-write (capture decisions) → docs-sync. Use when "the test suite is bad" or you've hit the test-cleanup-bails-at-the-gate failure mode.

Design and implement robust Python tests with pytest, including unit and integration boundaries, fixtures, parametrization, failure cases, and optional property-based tests. Use when adding tests, repairing a test suite, or deciding how Python behavior should be verified.

Generic webapp QA fallback — use only when no project-specific QA skill applies (project-local QA wins; native builds → mobile-emulator-test). Use when "QA the app", "test CRUD", or "smoke test". Monkey / guest vs logged-in → test-exploratory. Dead buttons → plan-stub-checker. Pixel diffs → test-visual-regression.

Applies practical test-first and regression testing to behavior changes, bug fixes, state transitions, and public contracts.

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Test C# MCP servers at unit and integration levels using xUnit, Moq, and the MCP client SDK.

Guides test-driven development with a red-green-refactor loop, emphasizing behavior-focused tests and vertical slicing over horizontal test writing.

Generates Playwright-based browser end-to-end tests for Adobe App Builder SPAs and AEM extensions, including configs, test files, and CI workflows.

Close the PDCA loop on this session's diff. Headed playwright-cli, fix as you go. Use when "test my changes", "PDCA this". Pixel diffs → test-visual-regression. Story CRUD → test-qa. Monkey / guest vs logged-in → test-exploratory.

AL App/Test project layout diagnosis for Business Central. Use when the main app compiles test sources, AL0297 appears on test object IDs, Library Assert or Library - Sales is missing, test/app.json is not recognized, or a multi-root workspace with app and test projects needs diagnosis.

Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing, browser testing with Playwright, and linting.

Generate wrapper interfaces, default implementations, and DI registration code to make hard-to-test static dependencies in C# testable, using built-in abstractions like TimeProvider or custom wrappers.

Write tests before implementation code for new features, bug fixes, and refactoring, following the red-green-refactor cycle.

Write test-driven Laravel applications using PHPUnit, Pest, model factories, HTTP tests, Sanctum authentication testing, mocking, and coverage.

Design rigorous A/B tests with clear hypotheses, controlled variants, appropriate metrics, and sample size calculations.

Guides test-first development with vertical slices, writing one behavior test at a time and refactoring only when green.

Acceptance-test newly added features using browser automation, happy-path flows, screenshots, UX notes, and a written report.

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

Designs A/B tests with sample size calculation, statistical significance testing, and result interpretation

Big Data Based Testing Skill