Results for “test”

Design and evaluate A/B tests with power, sample size, and robust metric interpretation. Use when: (1) planning controlled experiments, (2) reading p-values/effects, (3) sequential testing safeguards. NOT for: dark-pattern optimization.

A/B and multivariate testing methodology. Design experiments, calculate sample sizes, determine statistical significance, avoid common pitfalls, and interpret results. Platform-agnostic framework applicable to landing pages, emails, ads, pricing, and product features. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, or conversion experiments.

xUnit.net testing framework with Fact, Theory, fixtures, DI, and mocking with Moq and NSubstitute. Covers .NET testing best practices. USE WHEN: user mentions "xUnit", ".NET testing", "Fact", "Theory", "InlineData", "Moq", "NSubstitute", "C# unit test" DO NOT USE FOR: NUnit - use `nunit`, Vitest - use `vitest`, Jest - use `jest`, Playwright - use `playwright`

Parse source files to find which ones have no test file referencing their declared types, producing a prioritized worklist of untested files.

Exploits the MS17-010 (EternalBlue) vulnerability in Microsoft's SMBv1 implementation for authorized security testing, red team exercises, and penetration testing engagements.

Refactors production code with test coverage using a TDD workflow that applies approved refactorings one at a time, gates each on passing tests, and commits or reverts accordingly.

Use only for video game projects; design playable prototype tests and success criteria for fun, clarity, and replay

Screenshot-obsessed, fantasy-allergic QA specialist - Default to finding 3-5 issues, requires visual proof for everything

スキル定義（SKILL.md）を静的点検・ドライランで検証するスキル。 `--all` で全スキル一括健全性監査モード（ランキング＋修正案ドラフト生成）。 「スキルを点検して」「スキルをテストして」「スキルのバグ確認」「スキル検証」 「全部のスキルを点検して」「一括点検」または /skill-test を呼び出した時にトリガー。

Discover and exploit XML External Entity injection vulnerabilities to read server files, perform SSRF, and exfiltrate data during authorized penetration tests.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Recommends treating central hypothyroidism before performing GH stimulation testing because CH may impair accurate diagnosis of GHD. Use when preparing for GH stimulation testing; triggers include patient requiring GH stimulation test with possible CH.

Recommends against performing dynamic GnRH stimulation testing in the evaluation of hypogonadism, as it provides no additional diagnostic information beyond baseline gonadotropins and sex steroids. Consider this recommendation when evaluating hypogonadism and contemplating GnRH testing.

Pressure-test an idea through persona-driven interrogation until it hardens, proves out, or dies cheaply. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'.

Writes Behavior-Driven Development scenarios using Gherkin syntax to create executable specifications and test behavior.

Provides guidance and best practices for working with Cypress, covering setup, development, deployment, and troubleshooting.

Strict test-first gate only when explicitly requested or required by repository policy. Do not use for ordinary practical testing.

Master Test Architect and Quality Advisor. Use when the user asks to talk to Murat or requests the Test Architect.

Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP), updating project files, CLI arguments, and CI/CD pipelines for MSTest, NUnit, and xUnit.net.

Test web applications for XML injection vulnerabilities including XXE, XPath injection, and XML entity attacks to identify data exposure and server-side request forgery risks.

Safely change and test untested codebases using techniques from Feathers' 'Working Effectively with Legacy Code': seams, characterization tests, sprout/wrap, and dependency-breaking.

Maps external dependencies and I/O boundaries, generates chaos tests for failure modes like timeouts and connection errors, runs them, and reports resilience gaps with fixes.

Impersonate a user in Apex tests with System.runAs to verify sharing, profile, and permission-set behavior, and to work around mixed-DML errors in test setup.

Guides users through the specification-driven development workflow, from requirements gathering through specification, test derivation, implementation, and validation.

Use when designing or implementing tests for TypeScript behavior, public types, compiler failures, filesystem or process boundaries, or package-consumer compatibility.

Readability Review

Validates, tests, and scores the quality of skills within a claude-skills ecosystem using Python scripts that check structure, syntax, runtime, and multi-dimensional quality metrics.

Write the context brief a first-time tester gets before testing an app, tool, codebase, or product — it explains WHAT the thing is and why it exists, while deliberately withholding HOW anything works. The companion to the fresh-eyes skill; the brief it produces is the "starting information" handed to a fresh-eyes tester. Use this whenever the user is preparing a fresh-eyes or first-time-user test and needs the setup material, or says things like "describe my app without giving anything away", "write the context card for the tester", "explain what it is but not how to use it", "set up the newcomer test", "what would the tester be told going in?", or wants a spoiler-free description of their product. Also use it when someone asks for the briefing/intro that a new tester, new hire, or evaluator should receive before first contact with the thing being tested.

Find root causes of bugs, test failures, or unexpected behavior before proposing any fixes.

Review pull requests following Sentry engineering practices, covering security, performance, testing, and design.

Automates browser interactions for web testing, form filling, screenshots, and data extraction.

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

Coordinates five specialized coding agents (linter, perf, refactor, security, test) to enforce quality gates across the development lifecycle, from lint enforcement through performance profiling, refactoring, security auditing, and test coverage.

This skill should be used when the user asks to "set up a web server", "configure HTTP or HTTPS", "perform SNMP enumeration", "configure SMB shares", "test network services", or needs guidance on configuring and testing network services for penetration testing labs.

This skill should be used when the user asks to "set up a web server", "configure HTTP or HTTPS", "perform SNMP enumeration", "configure SMB shares", "test network services", or needs guidance on configuring and testing network services for penetration testing labs.