







Welcome to "The Fuzzing Book"! Software has bugs, and catching bugs can involve lots of effort. This book addresses this problem by automating software testing, specifically by generating tests automatically. Recent years have seen the development of novel techniques that lead to dramatic improvements in test generation and software testing. They now are mature enough to be assembled in a book – even with executable code.
Fuzzing
Fuzzing represents a dynamic testing method that inputs malformed or unpredictable data to a system to detect security issues, bugs, or system failures.
Start Fuzzing With Zig
Fuzzing is a testing technique in which a program generates random data as input for another program to consume. The goal is to find data which could cause corruption or other fatal issues in the software that is being tested.
fuzzdb-project/fuzzdb
Dictionary of attack patterns and primitives for black-box application fault injection and resource discovery.
Test-Driven Approaches to Software Engineering with Large Language...
Tests increasingly participate in the decisions made by large language models and software engineering agents. They specify intended behavior, guide program construction and repair, select...

On the Risks of using LLM-Generated Tests for Regression Testing
Software is under constant evolution: developers continuously add features, fix bugs, and refactor code, and any of these changes may break existing functionality. Regression testing guards against such effects by capturing expected behavior in test cases. LLM-based test generation aims to automate this process by generating regression tests directly from the code under test. This is beneficial when the implementation is correct, but problematic when the code contains faults: the generated tests may then encode and preserve incorrect behavior. To investigate this risk, we apply LLM-based regression test generation to pull requests merged into the main branch of software projects and study the impact of the generated tests on subsequent project evolution. We distinguish between fault-revealing tests, which assert correctly implemented behavior, and fault-enforcing tests, which assert faulty behavior. Across 145 pull requests from SciPy, Qiskit, and pandas, 8%-17% of the generated tests are fault-enforcing, while only 2.4%-4.8% reveal faults. Fault-enforcing tests persist over time: after several subsequent commits, 83%-91% of them are still relevant and pass. They also accumulate: when the faults of all pull requests are combined in one codebase, 83%-92% remain enforced at the end of the commit history, and the developer-written test suite detects only 14%-30% of them. Our results reveal a fundamental risk of LLM-generated regression tests: without manual validation, they may encode faulty behavior as expected behavior, allowing bugs to persist across software revisions and largely evade developer-maintained test suites. LLM-based regression testing can thus give rise to a new form of technical debt.

Testing can be fun, actually
Writing and maintaining tests is boring. But they're also some of the most valuable code we can write. With this blog post you'll learn a criminally underrated testing technique to add to your testing toolbox that can make tests a whole lot more pleasant.

The value of human, exploratory testing
Ann and Michael find things programmers never would have.Since unit testing and test-driven development burst onto the programming scene in the early 2000s, too many programmers have deluded themse…
SpaceDucking — Practice software testing
Duck-themed practice apps full of deliberate bugs, plus a members-only bug database.

Ephemeral testing
We have many ways to ensure software quality. Unit testing. Fuzz testing. Integration testing. And so forth. I'd like to propose a method that was unthinkable before: ephemeral testing. (Ephemeral is a fancy word for 'throw away' or 'temporary'.) You write your code. You build your software component. Or the AI agent does … Continue reading Ephemeral testing

A new era for software testing - <antirez>
Testing Titbits Playground - Free games for software testers
A free games portal for software testers. Sharpen your testing, debugging and AI intuition with quick, replayable browser games.

Fuzz Map
Fuzz Map is a fuzzer for GUIs that automatically identifies states using code coverage and builds a visual map. Ideally, the map is useful even to people who'd prefer not to read code.
</> htmx ~ Codin' Dirty
In this article, Carson Gross discusses an alternative approach to software development that challenges the principles outlined in 'Clean Code.' Carson advocates for allowing larger functions in certain cases, preferring integration tests over unit tests, and minimizing the number of classes and interfaces. He shares examples from successful software projects that demonstrate these practices can lead to maintainable, high-quality code.

Commix Project | Automated All-in-One OS Command Injection Exploitation Tool.
Automated exploitation of command and code injection flaws, from detection to full control of the underlying operating system.
How we built an automated unit test generation pipeline for iOS
We generated 85K lines of iOS tests with minimal manual effort.
