mirror of
https://github.com/vector-im/element-web.git
synced 2025-09-19 12:41:24 +02:00
Merge pull request #15050 from vector-im/jryans/testing-code-review
Add testing to review guidelines
This commit is contained in:
commit
cb94a89411
@ -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
|
||||||
|
Loading…
x
Reference in New Issue
Block a user