anchor.diff:  image::images/customize-data-views-menu.tiff[]
   
   image::images/customize-data-views.png[]
  +
  +=== Performing code coverage
  +
  +When performing code coverage, you might wanty to exclude `AbstractBytes` as this significantly slows down the running of unit tests.
positive.code: 
  Once you have your data dumped as hexadecimal, you can create tests using that data, and make variations of those tests.
  
  ==== What do we mean by a Lambda function?
  
  In this context a Lambda function is one which is entirely input driven and produces a list of messages (one or more outputs).
  
  The simplest Lambda function is stateless, however this has limited application.  They are useful for message translation.
  
  If you need a stateful Lambda function, you can consider the input to the function to be every message it has ever consumed.
  Obviously this is inefficient, however with appropriate caches in your lamdba function, you can process and produce result incrementally.
  
  ==== Data in and out.
  
  We module a Lambda function as having an interface for inputs and another for outputs.  These interfaces can be the same.
  
  .Sample interface for Lambda function
  [source, Java]
  
negative.code: 
  In this case, the test calls the methods with the matching method ids which in turn uses the same ids to encode the output.
  
  NOTE: Creating and maintain such tests can be an overhead you don't need.In this case, you can use Chronicle Wire's YAML testing format to check functionality.WIre can be used for most of the tests even if you intend to use Bytes for production.
  
  === Comparison of access to native memory
  
  