Results for “t-test”

Tests WebSocket API implementations for security vulnerabilities including missing authentication, Cross-Site WebSocket Hijacking, injection attacks, and denial-of-service.

Test GraphQL APIs for depth limit vulnerabilities by sending deeply nested recursive queries to identify denial-of-service risks.

Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations, analyzing a project to identify repositories, DAOs, and service layers that interact with the database, then producing a structured testing plan.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness

Guides coding workflows with planning, implementation, verification, and testing, storing user preferences locally on request.

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

Validate procurement workflows, skills, data extraction, compliance, and integration with systematic testing methodology for procurement domain

Use this skill when the user asks about commercial driver drug & alcohol testing under 49 CFR 382 + 40 — the six testing reasons (pre-employment, random, post-accident, reasonable suspicion, return-to-duty, follow-up), MRO process, SAP/return-to-duty process, post-accident triggers, random selection rates, what panels are tested, refusal definitions, or testing programs and consortiums. Cite specific 49 CFR 382 or 40 subsection.

Use when planning how to test any deliverable or system. This skill provides a framework for selecting the right testing approach based on what is being delivered, ensuring comprehensive coverage without unnecessary overhead.

Launches a Flutter app on a simulator or emulator, generates and runs exhaustive integration tests covering every screen, button, form, and user flow, then self-heals failures.

Conduct a comprehensive external network penetration test to identify vulnerabilities in internet-facing infrastructure using PTES methodology, reconnaissance, scanning, exploitation, and reporting.

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions, including A/B testing, sample size estimation, and statistical interpretation.

Configure and test common network services (HTTP, HTTPS, SNMP, SMB) for penetration testing lab environments, enabling hands-on practice with service enumeration, log analysis, and security testing.

Verify implemented work meets acceptance criteria — run tests, check PHPCS, validate Blade output, lando phpunit, lando phpcs, lando yarn test, Playwright tests, accessibility check, post-implementation verification, done criteria validation, checklist review, verification phase

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.

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 this skill for fuzz tests for parsers, APIs, file handlers, encoders, validators, security-sensitive inputs. Trigger when the task involves security work related to Fuzzing Security Tests, implementation, audits, debugging, strategy, or validation.

Perform dynamic security testing against running web applications and APIs to discover vulnerabilities through active probing and fuzzing. Use when the user requests dynamic application security testing or provides relevant inputs for this workflow.

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

Tests authentication and authorization mechanisms in mobile application APIs to identify broken authentication, insecure token management, session fixation, privilege escalation, and IDOR vulnerabilities.

Identifies and exploits SQL injection vulnerabilities in web applications during authorized penetration tests using manual techniques and automated tools like sqlmap.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

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

Guides setting up CI/CD pipelines with GitHub Actions, testing, and deployment strategies.

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

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

API backend test generation for Nick's stack, especially Next.js App Router APIs with Supabase-aware auth assumptions. Use when testing backend routes, generating API test suites, validating authenticated vs unauthenticated access, checking malformed inputs, or building route-by-route backend coverage for projects that use /app/api or /pages/api.

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