anchor.diff:  Glad you asked. Because of Arquillian Governor base extension, you are welcome to code 
   your own test method execution resolver as we did with Arquillian JIRA governor extension.
   
  -The governor annotation you want to put on your test method (as we did with +@Jira+) have 
  -to be annotated with +@Governor+ annotation. +@Jira+ annotation looks like this:
  +The governor annotation you want to put on your test method (as we did with `@Jira`) have 
  +to be annotated with +@Governor+ annotation. `@Jira` annotation looks like this:
   
   [source,java]
   ----
  
positive.code: Arquillian Governor extension is an extension on top of which all other concrete _governors_ are 
  built. When you provide some custom Governor implementation, this extension is automatically behind it. 
  Arquillian Governor base implementation is configured by putting the following extension definition
  into +arquillian.xml+ like this:
  
  [source,xml]
  ----
  
negative.code:     }
  ----
  
  If `status` is `Status.MANUAL`, test method will be skipped from the execution. The generated report gives you 
  better overview of your test cases, what they do, which methods are automated and which you have to execute manually.
  
  If `plainAdoc` property is used, a report will be saved to plain asciidoc table as well. A report will be 
  added into the tree of Arquillian Report output file in every case.
  
  |===
  |Configuration property|Description|Default value|Possible values
  
  |plainAdoc
  |name of file where plain asciidoc table will be stored
  |if this is not set, report to plain adoc will be skipped
  |
  