Implement a process for release to include automated testing

[mikeschinkel]

We need a release checklist, simple things like "Update /box/version" and we also need automated testing procedures.

Clear how to do this is far from obvious so this ticket can be the beginning of discussions for us:

The following are potentially useful links for tackling this issue (have not reviewed any of them yet):

• https://github.com/sstephenson/bats
• https://github.com/lehmannro/assert.sh
• https://stackoverflow.com/questions/1339416/unit-testing-bash-scripts
• https://unwiredcouch.com/2016/04/13/bash-unit-testing-101.html
• https://blog.engineyard.com/2014/bats-test-command-line-tools
• https://code.tutsplus.com/tutorials/test-driving-shell-scripts--net-31487
• https://conferences.oreilly.com/velocity/vl-ca-2016/public/schedule/detail/50217
• http://eradman.com/posts/ut-shell-scripts.html
• http://bashinator.org/
• http://blog.spike.cx/post/60548255435/testing-bash-scripts-with-bats
• https://www.ansorg-it.com/project/bashsupport/

[mikeschinkel]

@MickMake Is there more we need to discuss here, such as how to incorporate into the build system?