anchor.diff:  
   Examples suite is stored in a textual file named by the AST node (e.g. block_table, inline_anchor…, see the list below) with an extension according to its syntax (e.g. `block_table.adoc`, `block_table.html`) — similarly as Asciidoctor templates.
   Individual examples in the suite are separated by a special header with the name of the example, an optional description and options.
  -This header should enclosed as a comment (so you can render the examples suite as a valid AsciiDoc/HTML/TeX/… document).
   
   Each example is uniquely identified with its name and the suite name like this: `{suite_name}:{example_name}` (e.g. `block_table:with_title`).
   Input and output examples are paired — for every input example there should be an output example with the same identifier.
  -When you run test, the input example is converted using the tested backend (or templates) and its actual output is compared with the (expected) output example.
  +When you <<run-tests, run tests>>, the input example is converted using the tested backend (or templates) and its actual output is compared with the (expected) output example.
   
   [horizontal]
   .List of Asciidoctor’s AST nodes
  
positive.code: [source, sh]
  bundle exec rake test
  
  
  == Examples
  
  
negative.code: === Input examples
  
  DocTest provides a collection of the reference input examples that should be suitable for most backends.
  You can find them in link:data/examples/asciidoc[].footnote:[Since GitHub implicitly renders them as a plain AsciiDoc, you must view a Raw source if you want to see what’s going on here.]
  There are a lot of test examples and some of them may not be relevant to your backend — that’s okay, when some output example is not found, it’s marked as skipped in test.
  
  You can also write your own input examples and use them together with those provided (or replace them).
  