anchor.diff:   <li>switch to your new feature branch
    <li>build/amend the documents
    <li>provide screen images if needed
  - <li>provide test cases to confirm your documentation
  - <li>test and build everything
  + <li>provide test cases to match your documentation
  + <li>build and test everything
    <li>commit your changes
    <li>switch to your master branch
    <li>merge your branch full of changes into the master branch
  
positive.code:  ----
  ....
  
  would only insert source between the +BuilderSupportTest_add_node_with_value_object4+ tag start and end as follows : 
  
  image::assets/img/example19.png[BuilderSupportTest.groovy Listing] 
  
  
negative.code: ----
  
  
  === Forget Test Cases ?
  
  Well, why not ? It's not critical to have samples of test stuff. Plenty of great documentation does not require any reference to tests or the content may not even be about code, logic, tests, scripts.
  
  <<<
  
  == How To Write Documentation
  
  Review current [blue]#Groovy# documents to gain an understanding of how it's written and what sort of content it has. http://groovy-lang.org/json.html[Look at this page about Json]. It uses our latest document standards. Now you know about *tags* you can appreciate how test samples are picked from external sources.
  
  