Add annotations to each of the test systems to describe themselves.

The test files have now been updated to include annotations, in the
file prologue comment, which describe the test and its place in the
testing environment.

These are just a convention that I've used previously, but they help
to focus anyone doing testing on describing where they fit into the
testing of the system. Such descriptions make it obvious when reviewed
where there are gaps in testing.

examples/run_all_examples.py

@@ -1,6 +1,11 @@
 #!/usr/bin/env python
 """
 Run all the examples and collect the timings and results.
+
+SUT:    Invocation
+Area:   Examples run
+Class:  Functional
+Type:   System test
 """
 
 import argparse

tests/test_crash.py

@@ -1,3 +1,12 @@
+"""
+Test the fuzzing terminates when a fault is found.
+
+SUT:    Fuzzer
+Area:   Fault finding
+Class:  Functional
+Type:   Integration test
+"""
+
 import io
 import os
 import unittest

tests/test_nocrash.py

@@ -1,3 +1,12 @@
+"""
+Test the fuzzing terminates when no faults found, at a run limit.
+
+SUT:    Fuzzer
+Area:   Non-fault operation
+Class:  Functional
+Type:   Integration test
+"""
+
 import unittest
 
 try:

tests/unittest_mutators.py

@@ -1,3 +1,12 @@
+"""
+Test the mutators operate as desired.
+
+SUT:    Corpus
+Area:   Mutators
+Class:  Functional
+Type:   Unit test
+"""
+
 import unittest
 
 try: