Test your Code Review knowledge with a free interactive quiz — 28 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
A reviewer leaves 30 comments on a PR, all about variable naming and formatting, none about the fact that the new endpoint has no authentication check. What is the core problem with this review?
In this round
A reviewer leaves 30 comments on a PR, all about variable naming and formatting, none about the fact that the new endpoint has no authentication check. What is the core problem with this review?
What is the risk of a reviewer treating every comment -- from a security bug to a naming preference -- with the same urgency and tone?
A reviewer disagrees with an author's architectural choice but is not fully certain their alternative is better. What is the most constructive way to phrase the comment?
What does it mean to "comment on the code, not the person"?
A PR that fetches N users sequentially with `await` inside a for-of loop, when the fetches are independent and could run via `Promise.all`, is best flagged as:
A reviewer writes: "Why would you write it this way? You always do this." What is wrong with this comment?
What does approving a PR "with comments" typically signal?
Why do small, focused PRs generally get better reviews than large ones?
A comment thread on a PR has gone back and forth five times between the author and reviewer without resolving. What is the recommended next step?
A PR handler receives `req.body.userId` and uses it directly in a SQL query string via concatenation. What should the reviewer flag, and how urgently?
A PR adds a webhook handler that processes payment events without verifying the webhook signature. How should a reviewer categorize this comment?
What is the etiquette risk of leaving a PR with no response at all -- neither approval, comments, nor "changes requested"?