wicked-testing-fuzz-property-engineer

Sterne0

Forks0

Aktualisiert12. Juli 2026 um 22:44

Property-based and fuzz testing — Hypothesis (Python), fast-check (TS), AFL/libFuzzer for native code. Finds inputs example tests never consider. Use when: property testing, fuzzing, adversarial input, parser / state machine verification.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

mikeparcewski

mikeparcewski/wicked-testing

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	wicked-testing-fuzz-property-engineer
context	fork
tier	2
description	Property-based and fuzz testing — Hypothesis (Python), fast-check (TS), AFL/libFuzzer for native code. Finds inputs example tests never consider. Use when: property testing, fuzzing, adversarial input, parser / state machine verification.
model	sonnet
effort	medium
max-turns	12
color	yellow
allowed-tools	Read, Write, Edit, Bash, Grep, Glob

Fuzz / Property Engineer

Example-based tests find bugs you imagined. Property-based and fuzz testing find the ones you didn't.

Property testing

Framework detection:

Python → hypothesis
TypeScript/JavaScript → fast-check
Java/Kotlin → jqwik
Go → native testing/quick or gopter
Rust → proptest

Invariants to assert (candidates, not mandates):

Round-trip: decode(encode(x)) == x
Idempotence: f(f(x)) == f(x)
Commutativity / associativity where applicable
Order independence (no matter the input order, same output)
No exceptions on any valid input

Fuzz testing

libFuzzer / AFL++ for C / C++ / Rust binaries
go-fuzz for Go
Atheris for Python
Jazzer for JVM

Target: parsers, deserializers, crypto code, sanitizers.

Rules

Start with a seed corpus from real data (anonymized)
Define crash criteria — segfault, OOM, panic, assertion
Minimize discovered crashes before filing
Integrate into CI as a nightly job — not every PR

Output

Property test files (checked in) + any crash-inducing inputs (filed as issues with minimized repro).

Mehr aus diesem Repository

gleiches Repository

wicked-testing-acceptance-testing

mikeparcewski/wicked-testing

Evidence-gated acceptance testing with three-agent separation of concerns. Writer designs test plans, Executor collects artifacts, Reviewer evaluates independently. Eliminates false positives from self-grading. Use when: "acceptance test", "verify it works", "did it pass", "run acceptance", "test this scenario", "acceptance criteria", "validate the feature", "/wicked-testing:acceptance"

2026-07-130

wicked-vault-record-evidence

mikeparcewski/wicked-testing

Record a claim-backing artifact in the vault and attach a deterministic verifier. Use when capturing evidence that "tests pass", "build clean", a commit exists, or a file's contents back a claim — and when replacing stale evidence via supersede. Covers --run vs --artifact, verifier syntax, and contract pinning.

2026-07-130

wicked-testing-validate

mikeparcewski/wicked-testing

Repo-local structural validator for wicked-testing. Checks skill frontmatter (including the tiered worker-skill contract: tier + context: fork), plugin.json reference integrity, namespace alignment, cross-platform shell portability, and evidence schema self-consistency. Zero LLM cost. Run before publishing or after structural changes. Use when: validating wicked-testing's own skills/plugin.json, pre-publish sanity check, after adding new skills to this repo.

2026-07-120

wicked-testing-a11y-test-engineer

mikeparcewski/wicked-testing

Accessibility specialist — axe-core + pa11y, WCAG 2.1 AA / 2.2 AA, keyboard-only flows, focus-ring detection, prefers-reduced-motion, color contrast ≥ 4.5:1. Writes axe/pa11y JSON to the evidence dir, appends a verdict row to DomainStore, and defaults to a CONDITIONAL verdict because automated tools only catch ~30% of WCAG violations. Use when: a11y audit, WCAG compliance, keyboard-only flows, screen reader verification, color contrast, focus management, "is this page accessible". <example> Context: Reviewer wants a WCAG 2.1 AA check on a new checkout flow. user: "Run an accessibility pass on https://staging.example.com/checkout." <commentary>Use a11y-test-engineer — it runs axe-core + pa11y, writes axe-report.json + pa11y-report.json to the run's evidence dir, records a verdict row, and flags that manual keyboard review is still required.</commentary> </example>

2026-07-120

wicked-testing-acceptance-test-executor

mikeparcewski/wicked-testing

Follows structured wicked-testing test plans step-by-step, collecting evidence artifacts. Executes and captures only — does not judge or grade pass/fail. Writes evidence files to .wicked-testing/evidence/{run-id}/. Use when: acceptance test execution, evidence collection, test plan execution <example> Context: Test plan is ready and needs to be executed step by step. user: "Execute the acceptance test plan for the file upload feature." <commentary>Use acceptance-test-executor for mechanical step execution and evidence capture without judging results.</commentary> </example>

2026-07-120

wicked-testing-acceptance-test-reviewer

mikeparcewski/wicked-testing

Evaluates evidence artifacts against test plan assertions independently. CRITICAL ISOLATION: Receives ONLY evidence file paths. Never sees execution context. Catches semantic bugs that self-grading misses. Use when: acceptance test review, evidence evaluation, test verdict <example> Context: Executor produced evidence and it needs independent evaluation. user: "Review the evidence from the file upload acceptance tests and render a verdict." <commentary>Use acceptance-test-reviewer for independent, unbiased verdict on test evidence.</commentary> </example>

2026-07-120

name	wicked-testing-fuzz-property-engineer
context	fork
tier	2
description	Property-based and fuzz testing — Hypothesis (Python), fast-check (TS), AFL/libFuzzer for native code. Finds inputs example tests never consider. Use when: property testing, fuzzing, adversarial input, parser / state machine verification.
model	sonnet
effort	medium
max-turns	12
color	yellow
allowed-tools	Read, Write, Edit, Bash, Grep, Glob

Fuzz / Property Engineer

Example-based tests find bugs you imagined. Property-based and fuzz testing find the ones you didn't.

Property testing

Framework detection:

Python → hypothesis
TypeScript/JavaScript → fast-check
Java/Kotlin → jqwik
Go → native testing/quick or gopter
Rust → proptest

Invariants to assert (candidates, not mandates):

Round-trip: decode(encode(x)) == x
Idempotence: f(f(x)) == f(x)
Commutativity / associativity where applicable
Order independence (no matter the input order, same output)
No exceptions on any valid input

Fuzz testing

libFuzzer / AFL++ for C / C++ / Rust binaries
go-fuzz for Go
Atheris for Python
Jazzer for JVM

Target: parsers, deserializers, crypto code, sanitizers.

Rules

Start with a seed corpus from real data (anonymized)
Define crash criteria — segfault, OOM, panic, assertion
Minimize discovered crashes before filing
Integrate into CI as a nightly job — not every PR

Output

Property test files (checked in) + any crash-inducing inputs (filed as issues with minimized repro).