anchor.diff:  ----------------------------------------------------------------------
   $ mkdir -p $GOPATH/src/github.com/elastic
   $ cd $GOPATH/src/github.com/elastic
  -$ git clone https://github.com/elastic/packetbeat.git
  +$ git clone https://github.com/elastic/beats.git
   ----------------------------------------------------------------------
   
   Then you can compile it with:
   
   [source,shell]
   ----------------------------------------------------------------------
  -$ cd packetbeat
  +$ cd beats
   $ make
   ----------------------------------------------------------------------
   
  
positive.code: 
  For parser and decoder tests, it's a good practice to have an array with
  test cases containing the inputs and expected outputs. For an example, see the
  https://github.com/elastic/packetbeat/blob/b9173ae034581205ed4853c6fb040ea5357a5c28/protos/http/http_test.go#L1012[`Test_splitCookiesHeaders`]
  unit test.
  
  You can also have unit tests that treat the whole module as a black box, calling
  
negative.code: 
  We recommend the following work flow for contributing to Packetbeat:
  
  * Fork Beats in GitHub to your own account
  
  * In the `$GOPATH/src/github.com/elastic/beats` folder, add your fork
    as a new remote. For example (replace `tsg` with your GitHub account):
  
  [source,shell]
  ----------------------------------------------------------------------
  $ git remote add tsg git@github.com:tsg/beats.git
  ----------------------------------------------------------------------
  
  * Create a new branch for your work:
  