This is the code review model I've arrived at after going through a number of different processes throughout my career: Code review is a health check from your

This is the code review model I've arrived at after going through a number of different processes throughout my career: Code review is a health check from your teammates who don't have the authorship bias. It is not a replacement for testing, both manual and automated. Testing is solely the responsibility of the author, code review is just a design lint check and/or knowledge sharing opportunity. You can still have a QA team of course, but that is usually decoupled from application development and is done post-merge anyway. Every shop is different so YMMV, this is just a personal take.