Parameterized, Property-Based, and Fuzz Testing Capabilities

[moodmosaic]

Traditional example-based testing falls short in covering the wide array of input combinations and edge cases:

• each test executes once, with concrete input values. That is, unit test functions are public and without parameters.

---

As our ecosystem grow more sophisticated, the testing methods must evolve to identify vulnerabilities and ensure contract robustness:

• at the very least, each test must be able to run multiple times with randomly generated concrete values (smaller values, à la property-based testing).

(From there, via Clarinet config/flag, you can tell to the underling data generator to be biased, and then you'll have turned your property-based tests to look more like fuzz tests—one of the reasons why foundry uses that terminology as well. 🔢)

To summarize:

type	prefix	arguments	semantics
concrete	test	no	single execution with concrete values (you are here)
property	test	yes	multiple executions with randomly generated concrete values (smaller values)
fuzz	test	yes	multiple executions with randomly generated concrete values (biased)

---

See also:

• https://github.com/dapphub/dapptools/tree/master/src/dapp#property-based-testing
• https://fv.ethereum.org/2020/12/11/symbolic-execution-with-ds-test/#using-ds-test
• https://github.com/crytic/echidna?tab=readme-ov-file#writing-invariants
• https://book.getfoundry.sh/forge/advanced-testing
• Implement improved testing structure citycoins/protocol#3 (comment)
• clarinet fuzz command and heterogeneous test-suites hirosystems/clarinet#398
• Integrate Clarinet devnet SDK in integration tests sbtc#352
• How to run the tests PromptECO/clarity-sequence#4 (comment)

[moodmosaic]

This can be added to the list: https://x.com/PatrickAlphaC/status/1624137622510571522.