Reproducibility and testing: Documenting best practices for code testing and code review

[danielskatz]

No description provided.

[dangunter]

There may be two useful and independent topics here: general principles, and technologies. The former would be more stable and broadly applicable, and the latter would depend on the project. Although for technologies there are definitely some common patterns on GitHub that could probably be reused across a number of projects. In KBase we are ramping up on TravisCI and GitHub pull-requests along with codecov.io. I think this is one common toolset that should be mentioned explicitly. It does create an interesting tension with a tool like Jira; PRs and Jira issues overlap to some extent, and they each have their advantages.