GPT-5.6 Sol vs Qwen3.7 Max for code review

The verdict

GPT-5.6 Sol wins, 9688

Same 12 code review tasks, marked blind by three rival labs. GPT-5.6 Sol took 8 tasks, Qwen3.7 Max took 0, 4 tied. Tested 18 Aug 2026.

Where they differed most

The task — The review, as JSON

Review this function and reply with ONLY valid JSON — no prose before or after, no commentary. 1 function initials(fullName) { 2 return fullName.split(' ').map(p => p[0].toUpperCase()).join(''); 3 } It is called with values taken from a free-text form field. Return an object with exactly these keys and no others: defects (an array, empty if there are none, each item an object with keys line (number), severity (one of 'high', 'medium', 'low'), issue (string), trigger (string — the input that causes it), fix (string)), and verdict (one of 'block', 'comment', 'approve').

{"defects":[{"line":2,"severity":"high","issue":"Empty segments cause p[0] to be undefined, so calling toUpperCase() throws a TypeError. This occurs for empty input and for leading, trailing, or repeated spaces.","trigger":"Ada  Lovelace","fix":"Normalize and validate the input before mapping, for example: fullName.trim().split(/\\s+/u).filter(Boolean).map(p => p[0].toUpperCase()).join(''), with an explicit empty-string result when the trimmed input is empty."},{"line":2,"severity":"medium","issue":"Splitting only on the literal space character…
{
  "defects": [
    {
      "line": 2,
      "severity": "high",
      "issue": "TypeError when input contains consecutive, leading, or trailing spaces, or is empty. split(' ') produces empty strings, making p[0] undefined, which throws on .toUpperCase().",
      "trigger": "'John  Doe' or '' or ' '",
      "fix": "Filter out empty strings before mapping: fullName.split(' ').filter(Boolean).map(p => p[0].toUpperCase()).join('')"
    },
    {
      "line": 2,
      "severity": "medium",
      "issue": "TypeError if fullName is null or undefined…

Task by task

TaskGPT-5.6 SolQwen3.7 Max
The pagination that skips page one98
Nothing wrong with it109
Three things wrong in six lines99
Two customers, one last item109
Rank by what breaks99
The review, as JSON108
Slow is not the same as wrong109
Overdue at one in the morning108
Write only the comment109
The complaint that is not a defect99
Right, and unusable109
Refuse the rubber stamp99

Full receipts: GPT-5.6 Sol, Qwen3.7 Max · judges claude-sonnet-5, gemini-3.1-pro-preview, grok-4.5

Questions people ask

Which is better for code review: GPT-5.6 Sol or Qwen3.7 Max?

GPT-5.6 Sol — it scored 96/100 against 88/100 on our 12-task code review suite, winning 8 tasks to 0 with 4 tied. Every answer was marked blind by three judges from three rival AI labs.

How was this tested?

Both models answered the identical published code review tasks. Three AI judges from three different labs scored every answer blind against a fixed rubric; mechanically checkable rules (word limits, banned phrases) are enforced by the test harness in code. The raw outputs and judge verdicts are downloadable.

More code review head-to-heads: GPT-5.6 Luna vs GPT-5.6 Sol · GPT-5.6 Sol vs GPT-5.6 Terra · GPT-5.3-Codex vs GPT-5.6 Sol · GPT-5.5 vs GPT-5.6 Sol · Claude Sonnet 5 vs GPT-5.6 Sol · GPT-5.6 Sol vs Grok 4.5

Full ranking: Best AI for code review · model pages: GPT-5.6 Sol, Qwen3.7 Max