title: clover: how does it work?
body: <p>I am evaluating clover currently and wonder how to use it best. First I'd like to understand how it works conceptually.</p>
  
  <p>1) What does instrumentation mean? Are the test-calls attached to implementation's statements? </p>
  
  <p>2) How is this done? Are the tests actually executed with some fancy execution context (similar to JRebel e.g.) for this? Or is it more like static analysis ?</p>
  
  <p>3) After a "clover-run", some DB is saved to disk, and based on this, reports are generated right? Is the DB-Format accessible? I mean Can I launch my own analysis on it, e.g. using my own reporting tools ? What information does the DB contain exactly? Can I see the mapping between test and implementation there ?</p>
  
  <p>4) Are there other tools that find the mapping between test and implementation? Not just the numbers, but which test, actually covers a line of code ...</p>
  
  <p>Thanks, Bastl.</p>