#!/usr/bin/env python
# coding: utf-8

# # Part II: Lexical Fuzzing
# 
# This part introduces test generation at the _lexical_ level, that is, composing sequences of characters.
# 
# * [Fuzzing: Breaking Things with Random Inputs](Fuzzer.ipynb) starts with one of the simplest test generation techniques: Fuzzing feeds a _string of random characters_ into a program in the hope to uncover failures.
# 
# * In [Getting Coverage](Coverage.ipynb), we measure the effectiveness of these tests by assessing their _code coverage_ – that is, measuring which parts of a program are actually executed during a test run.  Measuring such coverage is also crucial for test generators that attempt to cover as much code as possible.
# 
# * [Mutation-Based Fuzzing](MutationFuzzer.ipynb) shows how to _mutate_ existing inputs to exercise new behavior. We show how to create such mutations, and how to guide them towards yet uncovered code, applying central concepts from the popular AFL fuzzer.
# 
# * [Greybox Fuzzing](GreyboxFuzzer.ipynb) extends the concept of input mutation further, using statistical estimators to guide test generation towards likely bugs.
# 
# * [Search-Based Fuzzing](SearchBasedFuzzer.ipynb) takes the concept of guidance further, introducing search-based algorithms to systematically generate test data for a program.
# 
# * [Mutation Analysis](MutationAnalysis.ipynb) seeds synthetic defects (mutations) into program code to check whether the tests find them.  If the tests do not find mutations, they likely won't find real bugs either.