anchor.diff:  * Note how some PRs in this project have been reviewed by other developers. Here is an https://github.com/se-edu/addressbook-level4/pull/147[example].
   * Also note how we have used https://www.codacy.com[Codacy] to do automate some part of the code review workload (https://www.codacy.com/app/damith/addressbook-level4?utm_source=github.com&utm_medium=referral&utm_content=se-edu/addressbook-level4&utm_campaign=Badge_Grade[image:https://api.codacy.com/project/badge/Grade/fc0b7775cf7f4fdeaf08776f3d8e364a[Codacy Badge]])
   
  -Here are some things you can comment on when reviewing code:
  -
  -* Read the code from the perspective of a new developer. Identify parts that are harder to understand and suggest improvements.
  -* Point out any coding standard violations.
  -* Suggest better names for methods/variables/classes.
  -* Point out unnecessary code duplications.
  -* Check if the comments, docs, tests have been updated to match the code change.
  -* Check for violation of relevant principles such as the SOLID principles.
  -* Point out where SLAP can be improved. e.g. methods that are too long or has too deep nesting.
  -* Suggest any other code quality improvements.
  -
  -*Resources*
  -
  -* https://www.kevinlondon.com/2015/05/05/code-review-best-practices.html[Code Review Best Practices] - Blog post by Kevin London
  -* https://www.atlassian.com/agile/code-reviews[Why Code Reviews Matter] - An article by Atlassian
   
   === Exercise: Review a PR
   
  -* Review a GitHub PR created by a team member.
  +* Review PRs created by team members.
  
positive.code: The link:{repoURL}/src/test/java/seedu/address/commons/util/StringUtilTest.java[`StringUtilTest.java`]
  class gives some examples of how to use _Equivalence Partitions_, _Boundary Value Analysis_, and _Test Input Combination Heuristics_ to improve the efficiency and effectiveness of test cases testing the link:../src/main/java/seedu/address/commons/util/StringUtil.java[`StringUtil.java`] class.
  
  === Exercise: Apply Test Case Design Heuristics to other places
  
  * Find answers to these questions:
  ** What is an Equivalence Partition? How does it help to improve E&E of testing?
  ** What is Boundary Value Analysis? How does it help to improve E&E of testing?
  ** What are the heuristics that can be used when combining multiple test inputs?
  * Use the test case design heuristics mentioned above to improve test cases in other places.
  
  '''
  
negative.code: 
  === Exercise: Write more automated GUI tests
  
  * Covered by `[LO-SystemTesting]`
  
  '''
  
  