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
What is "rubber-stamping" in the context of code review?
In this round
What is "rubber-stamping" in the context of code review?
What is the benefit of a reviewer leaving a positive comment on a good decision in the diff, alongside their critical comments?
What does it mean to "comment on the code, not the person"?
Why is explaining the reasoning behind a requested change usually more effective than just stating the verdict?
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?
What is the etiquette risk of leaving a PR with no response at all -- neither approval, comments, nor "changes requested"?
A PR adds a webhook handler that processes payment events without verifying the webhook signature. How should a reviewer categorize this comment?
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:
What should a PR description ideally communicate, beyond what the diff itself shows?
Why does fast review turnaround (e.g. a first pass within a day) matter for team velocity?
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?
A PR adds a new database migration that drops a column. What should a reviewer check first?