testing

Probe implementations with adversarial tests to falsify correctness claims and produce reproducible verdicts.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill testing-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/testing
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill testing-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code is written, its own tests often confirm the author's assumptions rather than challenge them. This Skill applies independent, adversarial validation that tries to break the implementation, exposing edge cases, security holes, and contradictions before they reach production. ## Core Features & Use Cases - Adversarial Falsification: Treats every correctness claim as a hypothesis to disprove, attacking edge cases, malformed input, scale, concurrency, and security abuse paths. - Reproducible Evidence: Produces a clear verdict with reproducible failing cases and the exact verification commands that were run. - Regression Coverage: Adds a regression test for every defect found, complementing the engineer's test-first suite with boundary, negative, and cross-level tests. - Use Case: After an engineer ships a new API endpoint, use this Skill to attack it with null payloads, oversized inputs, and concurrent requests, then hand off a verdict with failing cases the engineer can reproduce. ## Quick Start Use the testing skill to adversarially probe the latest implementation for edge cases, malformed input, and security weaknesses, then report a verdict with reproducible failing cases.

Frequently Asked Questions about testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test code adversarially after implementation?▼

Run the existing test suite first, then attack the change with boundary values, empty or null inputs, malformed data, concurrency, and security abuse cases. Treat each correctness claim as a hypothesis to disprove and record reproducible failing cases.

What is the difference between adversarial testing and regular unit tests?▼

Unit tests written test-first confirm the engineer's own assumptions, while adversarial testing adds independent boundary, negative, cross-level, and security tests the author would not write. It aims to falsify claims rather than confirm them.

When should I use the testing phase versus the quality phase?▼

Use testing for dynamic, execution-based attacks on behavior, including dynamic security testing. Hand off to the quality phase for verification and validation, reviews, inspections, hardening review, and quality attributes beyond execution.

What should a testing verdict include?▼

A verdict should state whether the change survived adversarial probing, include reproducible failing cases for anything broken, and list the exact verification commands run. Every defect found should also gain a regression test.

Can visual or accessibility claims be validated by executable tests?▼

Behavioral claims require executable tests, but visual, accessibility, process, and quality claims need evidence appropriate to those claim types. The testing skill accepts non-executable evidence where execution cannot apply.