# A Proposed Property-Testing UX Inspired by AFL and OSS-Fuzz

DevFeed: [A Proposed Property-Testing UX Inspired by AFL and OSS-Fuzz](<https://devfeed.tech/articles/property-testing-like-afl-21959.md>)

Original publisher: [Read original article](<https://blog.nelhage.com/post/property-testing-like-afl/>)

Author: Nelson Elhage

Published: 2017-10-24T16:00:00Z

Content type: opinion

Language: en

Sources: [Nelson Elhage](<https://devfeed.tech/sources/nelson-elhage.md>)

Topics: [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [regression](<https://devfeed.tech/tags/regression.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ux](<https://devfeed.tech/tags/ux.md>)

## AI overview

The article examines common ground between property-based testing and fuzzing, then proposes a hypothetical property-testing user experience inspired by AFL and Google's OSS-Fuzz. It argues that regression test suites should be fast and reproducible so they can provide useful feedback during development.

## Source excerpt

In my last last post, I argued that property-based testing and fuzzing are essentially the same practice, or at least share a lot of commonality. In this followup post, I want to explore that idea a bit more: I'll first detour into some of my frustrations and hesitations around typical property-based testing tools, and then propose a hypothetical UX to resolve these concerns, which takes heavy inspiration from modern fuzzing tools, specifically the AFL and Google's OSS-Fuzz.