CMake Best Practices

Chapter 11: Automated Fuzzing with CMake

Software testing is crucial for ensuring that a software system behaves as expected. Unsurprisingly, the need for scenario-based testing strategies is still at its peak. But the scenario-based approach often does not suffice. The real world is wild. Things out there are not sterile as in a test environment. Many different variables contribute to a software's behavior. Environments, users, hardware, operating systems, or third-party libraries can affect software unexpectedly. As software becomes more extensive, it becomes painfully hard to come up with a testing suite that covers all possible aspects of it. Therefore, the need for a technique that performs the unexpected arises. Thankfully, fuzzing comes ...