Automate the testing of code and the generation of output

[jseldess]

This is a stretch project for 2.2.

• Automate the testing of code samples (driver/ORM and SQL)
  • This would help us catch any breakage between our samples and our product.
  • This may require storing all code in includes or even in a separate repository. See Code samples should be stored in a repo #3203 for more context.
  • For SQL, an approach would be to a consistent database for all examples. See Use MovR for docs examples - Phase 1 #2849.
  • For testing ideas, see Team City: Testing of examples #182.
• Automate the generator of SQL output
  • When the response format changes (rare), a large number of code blocks must be updated. This is not sustainable.
  • This may require code blocks with SQL output to be stored as includes.