anchor.diff:  
   IMPORTANT: Notice that instead of registering `arquillian-junit-container` as you usually do in Arquillian test, you are using `arquillian-junit-standalone`. This is because it has no sense to use in these kind of tests microdeployments feature (method annotated with `@Deployment`).
   
  -=== Test
  +==== Test
   
   Then the test looks like:
   
  
positive.code: = Introduction
  
  Usually when we talk about writing tests, the first thing that comes to your mind is some kind of static test where you send an input and you expect an output.
  
negative.code: 
  You can see full example at: https://github.com/arquillian/arquillian-cube-q/tree/master/ftest-pumba
  
  === Operative System Chaos
  
  
  To do *operative system chaos* Arquillian Q uses some modified version scripts of Netflix Simian Army project ().
  