anchor.diff:  
   The Auction package encodes the behavioral details around the [auction](./diego-auction.html).
   
  -It includes a simulation test suite that validates the correctness and performance of the auction algorithm.  The simulation can be run for different algorithms, at different scales.  The simulation can either be run in-process (for quick feedback loops) or across multiple processes (to understand the role of communication in the auction) or even across multiple machines in a cloud-like infrastructure (to understand the impact of latency on the auction).
  +It includes a simulation test suite that validates the optimality and performance of the auction algorithm.  The simulation can be run for different algorithm variants at different scales.  The simulation can be run in several ways: 
  +- In-process, for quick feedback loops
  +- Across multiple processes, to reveal the role of communication in the auction
  +- Across multiple machines in a cloud-like infrastructure, to reveal the impact of latency on the auction
   
   The [Auctioneer](./diego-pedia.html#auctioneer) and [Rep](./diego-pedia.html#rep) components use the Auction package to participate in the [auction](./diego-auction.html).
   
  
positive.code: 
  ### <a id='inigo'></a>Inigo
  
  Inigo is an integration test suite that launches the Diego components and excercises them through various test cases, including component failures and other exceptional cases.  As such, Inigo *validates* that a given set of component versions are mutually compatible, that the system of these components is robust, and that the performance of the system degrades gracefully.
  
  [**Inigo on GitHub**](https://github.com/cloudfoundry-incubator/inigo)
  
  
negative.code: 
  These tests exercise a number of happy-path test cases across the entire stack.
  
  Use the CF CLI to run the tests.
  
  [**Diego-Acceptance-Tests on GitHub**](https://github.com/cloudfoundry-incubator/diego-acceptance-tests)
  
  