Property Based Testing

What it does

The source focuses on behaviors that can be stated across many inputs, such as a round trip, ordering rule or invariant. It distinguishes a useful property from a test that generates data but asserts little. This helps an agent decide whether property-based testing adds evidence beyond a small set of existing examples.

Best for

Parsers, serializers, normalization functions, numerical rules and data structures with a clear relationship between inputs and outputs. Provide the intended contract and any invalid-input boundaries before selecting a generator.

Tradeoffs and requirements

A generated test can confidently enforce a wrong assumption. Random cases also do not replace integration or user-interface evidence. Framework and runtime setup depend on the project, and a codebase without an observable invariant may benefit more from focused example tests.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/trailofbits/skills/tree/2be6433b39e009cd2b6fd3be1895f6b1faa5af9a/plugins/property-based-testing/skills/property-based-testing --skill property-based-testing

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

70/100

70

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Write the invariant in plain language, define a valid input domain and add a small set of known examples. Generate cases, inspect failures and preserve a useful minimized example as a regression when appropriate.

How to judge the result

Check that the property fails against a deliberately incorrect implementation or a known defect. Review generator coverage, reproducibility and whether shrinking retained the condition that makes the failure meaningful.