Add testing to review guidelines

This adds a initial statement on testing to the review guidelines. No
requirements are made at this time, but reviewers are encouraged to request
tests where they believe it is reasonable to provide them.

Fixes https://github.com/vector-im/element-web/issues/14945
pull/15050/head
J. Ryan Stinnett 2020-08-26 15:57:31 +01:00
parent a3b8c67e79
commit bc1cad01c4
1 changed files with 2 additions and 0 deletions

View File

@ -14,6 +14,7 @@ When reviewing code, here are some things we look for and also things we avoid:
* Performance * Performance
* Accessibility * Accessibility
* Security * Security
* Quality via automated and manual testing
* Comments and documentation where needed * Comments and documentation where needed
* Sharing knowledge of different areas among the team * Sharing knowledge of different areas among the team
* Ensuring it's something we're comfortable maintaining for the long term * Ensuring it's something we're comfortable maintaining for the long term
@ -34,6 +35,7 @@ When reviewing code, here are some things we look for and also things we avoid:
* Reviewers should be explicit about required versus optional changes * Reviewers should be explicit about required versus optional changes
* Reviews are conversations and the PR author should feel comfortable * Reviews are conversations and the PR author should feel comfortable
discussing and pushing back on changes before making them discussing and pushing back on changes before making them
* Reviewers are encouraged to ask for tests where they believe it is reasonable
* Core team should lead by example through their tone and language * Core team should lead by example through their tone and language
* Take the time to thank and point out good code changes * Take the time to thank and point out good code changes
* Using softer language like "please" and "what do you think?" goes a long way * Using softer language like "please" and "what do you think?" goes a long way