EL: 03/09/2019

* Some discussion about which are the requirements about automated tests in issues has happened. While I think we have been 95% consistent, this is a brief summary, that mostly everybody agreed:

  > 0) automated tests are, always, welcome.
  > 1) new automated tests are required for changes in functionality (for sure that covers new features and improvements), not for bug fixes in general.
  > 2) there can be some bug fixes where coverage is desired. Both the tests labels (unit, behat, qa) and the followup strategies are acceptable.
  >
  > And about master, only about master, incomplete stuff is acceptable as far as it doesn’t break neither moodle neither testing. And all the follow for those issues are considered blockers. Must do.

* TODO:
  * Create a page in the dev docs with that strategy.
  * Point to it from important places (peer-review, integration, phpunit...).
  * Share with the community (exposed, chats...)