Re:Things Everyone Should Do: Code Review
by aaronblohowiak on Wednesday July 06, 2011 @09:13PM
(#2736729)
We pull the branch and have the reviewer run the relevant tests. Doing this was simpler than figuring out how to do fancy stuff with the ci server (which checks the integration branch after merge.).
Having this step requires the reviewer to know which tests are relevant, which ensures that they were written or updated.
If your source control makes branching/merging painful enough that it's going to get in your way to do it on a regular basis you might want something different, but that seems like an argument for better source control rather than a need for clever reviewing strategies.