fuzz-testing

Generate deterministic fuzz inputs to test Pact 5 smart contracts for boundary and invalid data handling.

1|1|Updated Jun 9, 2026

Search Tags:#testing #edge-cases #smart-contracts #fuzzing #boundary-values #type-confusion #pact-5

Ready to run

npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill fuzz-testing-pact-community-organization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fuzz-testing
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/fuzz-testing
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill fuzz-testing-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random and boundary input testing for Pact 5, enabling automated discovery of edge-case behavior, validation gaps, and unexpected failures in smart contracts.

Core Features & Use Cases

Boundary-value testing across numeric, string, and time inputs to reveal off-by-one errors and format exploits.
Type-confusion and empty-value testing to uncover robustness issues in contract handlers.
Reproducible fuzz patterns that help QA verify fixes across transfers, proposals, and chain-id logic.
Reporting of findings including unexpected behavior, gas spikes, and validation bypasses to guide fixes.

Quick Start

Run a fuzz test harness against a Pact 5 contract to surface edge-case inputs and document any anomalies.

Frequently Asked Questions about fuzz-testing

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

FAQPage Schema

How do I test Pact 5 smart contracts for boundary value and type confusion vulnerabilities?▼

Fuzz testing for Pact 5 involves generating focused inputs to probe boundary values, type confusion, and empty values across contract handlers. It surfaces validation gaps and unexpected failures in smart contracts by applying reproducible fuzz patterns to transfers, proposals, and chain IDs.

How do I set up a fuzz test harness for Pact 5 contracts?▼

Pact 5 fuzz testing covers numeric boundary values, type confusion, empty values, special strings, and decimal precision. It targets contract logic handling transfers, proposals, time values, and chain IDs to reveal off-by-one errors and format exploits.

Does Pact 5 fuzz testing work with a TypeScript test harness?▼

Yes, the generated deterministic fuzz patterns are explicitly designed for a TypeScript test harness. This allows you to automate edge-case input generation and execute targeted tests against Pact 5 smart contract handlers.

What specific edge cases should I test for in Pact 5 smart contract validation?▼

Findings from Pact 5 fuzz testing include unexpected behavior, gas spikes, and validation bypasses. Documenting these anomalies across transfers, proposals, and chain-id logic guides developers in fixing off-by-one errors and format exploits.

What kind of reporting does Pact 5 fuzz testing provide for smart contract anomalies?▼

Pact 5 fuzz testing reports unexpected behavior, gas spikes, and validation bypasses. Documenting these anomalies across transfers, proposals, and chain-id logic guides developers in fixing off-by-one errors and format exploits in contract handlers.