✳flâneur — a map of the web's best reading

Google Testing Blog: Code Health: Too Many Comments on Your Code Reviews?

testing.googleblog.com · 1,910 words · saved by 1 readers

Very informative and though-through article, Tom. Can you, please, comment more on actual code review tools you are using or can suggest to use in order to achieve better results. Thank you in advance. Hi Natali, I don't know about Google but I know that we have used Crucible/Fisheye as well as Bitbucket Pull requests, both integrate well with Jira and Confluence since they're all Atlassian products. Thank you, Paul. Actually we are trying them out within our organization as well. Hey, Natali, thanks for the kind words! I'm afraid I can't really advise on which tools to use. Google's main code review tool is proprietary. Android OS code goes via gerrit, which is alright, but I don't know how it compares to other externally-available code review tools. Thanks for the article. Also kindly check the "printer-friendly version" link. It seems to be broken. Thanks for the heads up! It appears to be working for us. What happens when you click the link? I goes to Google Docs page showing "You

Google Testing Blog: Code Health: Too Many Comments on Your Code Reviews? Testing Blog Code Health: Too Many Comments on Your Code Reviews? Monday, June 19, 2017 Google Labels: Code Health , Tom O'Neill , TotT 15 comments : Natali June 19, 2017 at 12:15:00 PM PDT Very informative and though-through article, Tom. Can you, please, comment more on actual code review tools you are using or can suggest to use in order to achieve better results. Thank you in advance. Reply Delete Replies Unknown June 20, 2017 at 2:51:00 PM PDT Hi Natali, I don't know about Google but I know that we have

Explore this link on the map →

related reading