Sounds like it's worth taking a step back and looking at your processes from a high level. If there's pressure to push code more quickly than is possible while

Sounds like it's worth taking a step back and looking at your processes from a high level. If there's pressure to push code more quickly than is possible while maintaining effective code reviews, then you may want to consider where that pressure is coming from. If velocity is causing quality control issues, then velocity is likely too fast. Not to mention that limiting quality checks will reduce velocity in the long term. Once you have both product and engineering (or whatever forces are at play) on the same page about reasonable expectations, I'd recommend using both. Code review and automated testing both serve distinct yet important roles.