As a developer, I always test my code locally before submitting a pull-request. I take the time to check off all the acceptance criteria and update the ticket to its current progress status. Once I submit a pull-request (PR), I ask my fellow developers to take a look and test the code on their local machines.
During the pull-request process, I am expecting to have an open conversation to explain my solution and how I believe it solved the issues on the ticket. It is also a good time for another member of the team to bring up something I might have missed or a different way of integrating. LISTEN and apply the changes requested if it makes sense.
This is also the ideal time to push back and implement best practices like documentation. Before any pull-request gets accepted the developer must provide updated documentation that represents the change being made. If the expectation is having documentation before the code is accepted, then your codebase will always have up to date docs.
PROTIP: Always have another member of the team accept the pull-request.