Should code reviewers reproduce the problem/solution as part of the code review?
Boss in upper management is demanding to know why code reviewers are attempting to reproduce the problem & solution (in the case of defects) and solution (in the case of features) for reasons of saving time. He insists this is only the job of the QA department and all we should be doing is looking at the code and nothing else. I have found it beneficial to do this. This both helps me understand the code better, gives me the perspective of the implementer, helps ensure they actually fixed it (and didn't miss anything), and so forth. Who is right here? If I am right what should I be telling the manager? Edit: for instance when submitting code for a pull request

Boss in upper management is demanding to know why code reviewers are attempting to reproduce the problem & solution (in the case of defects) and solution (in the case of features) for reasons of saving time. He insists this is only the job of the QA department and all we should be doing is looking at the code and nothing else.
I have found it beneficial to do this. This both helps me understand the code better, gives me the perspective of the implementer, helps ensure they actually fixed it (and didn't miss anything), and so forth.
Who is right here? If I am right what should I be telling the manager?
Edit: for instance when submitting code for a pull request