anchor.diff:  
   ################################################################################
   
  -# Testing organization. Use a new one each time because we cache the
  -# org_name -> org db id mapping in a few daemons.
  -org "pedant-testorg-#{Time.new.utc.strftime("%Y%m%d%H%M%S")}"
  +# Specify a testing organization if you are testing a multi-tenant
  +# instance of a Chef Server (e.g., Private Chef, Hosted Chef).  If you
  +# are testing a single-tenant instance (i.e. Open Source Chef Server),
  +# DO NOT include this parameter
  +#
  +# Due to how the current org cache operates, it is best to use a
  +# randomized name for your testing organization (hence the embedded
  +# Process.pid).  If you do not use a randomized name and run tests
  +# several times (destroying the organization between runs) you will
  +# likely get inconsistent results.
  +#
  +# If you wish Pedant to create the organization for you at test time,
  +# include the `:create_me => true` pair.  If you wish to use an
  +# existing organization for tests, you should supply a `:validator_key
  +# => "/full/path/to/key.pem"` pair
  +org({:name => "pedant-testorg-#{Process.pid}",
  +     :create_me => true})
   
  -# If you've specified a testing organization, you can also indicate
  -# whether or not Pedant should create this organization for you, or
  -# assume that it already exists.
  -create_org true
  +# org({:name => "existing_org",
  +#      :validator_key => "/etc/opscode/existing_org-validator.pem"})
   
   # If you want Pedant to delete the testing organization when it is
   # done, use this parameter.  Note that this only has an effect if
  
positive.code:     :superuser => {
        :name => "pivotal",
        :key_file => "/etc/opscode/pivotal.pem"
      }
    })
  
negative.code: # differs significantly from this.
  maximum_search_time 65
  
  # We're starting to break tests up into groups based on different
  # criteria.  The proper API tests (the results of which are viewable
  # to OPC customers) should be the only ones run by Pedant embedded in
  # OPC installs.  There are other specs that help us keep track of API
  # cruft that we want to come back and fix later; these shouldn't be
  # viewable to customers, but we should be able to run them in
  # development and CI environments.  If this parameter is missing or
  # explicitly `false` only the customer-friendly tests will be run.
  #
  # This is mainly here for documentation purposes, since the
  # command-line `opscode-pedant` utility ultimately determines this
  # value.
  include_internal false
  
  # Test users.  The five users specified below are required; their
  # names (:user, :non_org_user, etc.) are indicative of their role
  # within the tests.  All users must have a ':name' key.  If they have
  # a ':create_me' key, Pedant will create these users for you.  If you
  