anchor.diff:  `*** End of tc_[ETC name].TC_XXXX_[meaningful name] ***`
   Ex.: `*** End of tc_hla_declaration_management.TC_0001_Object_Publication ***`
   
  -=== GUI
  +==== GUI
   No GUI in the ETC, only parameters.
   
  -=== Results
  +==== Results
   The result of an ETC must be the following:
   * INCONCLUSIVE: Corresponds to an error during initialisation (preambleAction method) or termination (postambleAction method) of the test. It is equivalent to FAILED
   * FAILED: An error / a problem occurred during the execution of the ETC that leads to a failure
  
positive.code: 
  These rules were discussed between nations on 18 October 2016.
  
  == RTI compatibility
  The ETC must be developed and tested with both Pitch and MÄK RTI, last versions if possible.
  Some specific libraries (RTI adapters) will be developed in integrated in IVCT. ETC development must be done upon those RTI adapters.
  
  == Overall ETC structure
  
  === GitHub project name / Java package project name / Class names
  GitHub Repository name: TC_[ETC name]
  Ex.: `TC_CS_Verification`
  
  
negative.code: 
  **Warning:** The full name of a class may be very long. Ex.: `nato.ivct.etc.tc_hla_declaration_management.TC_0001_Object_Publication`
  
  ==== 3rd party libraries
  Because one of the main problem with Java development is the management of dependencies (i.e. librairies), _**all new development (new ETC) must use already existing libraries**_. It will avoid some inconsistency and incompatibility between codes developed by different developers that may use different versions of the same library.
  All 3rd party libraries must be declared in ETC Gradle files, as it is done in HelloWorld example.
  
  