arXiv paper· software engineering (LLM evaluation)· benchmark

WebCraftBench: Evaluating Web Application Generation from a Software Testing Perspective

Chenxu Liu, Zilu Zou, Peizhong Gao, Jiawen Tao, Zhexin Zhang, Guang Chen, Haowei Lin, Ying Zhou, et al.

cs.SE · cs.AI

Quick verdict

Coverage-guided interactive benchmark for LLM web-app generation; well-validated (85.3% human agreement) though dataset and code remain closed-source.

Summary

WebCraftBench is an interactive benchmark that evaluates LLM-generated web applications the way a software tester would. Generated apps are instrumented automatically with Istanbul-based tooling; an LLM agent using Playwright MCP then explores each application as a simulated user, guided by code coverage; interaction traces are condensed into a state-transition graph; and LLM judges score visual aesthetics, usability, and requirement alignment against 5,088 acceptance criteria spanning 369 real user requirements, with exploration deliberately separated from scoring. The authors evaluate 17 frontier models on all tasks (6,273 applications) and find complementary strengths: Claude-Opus-5 leads overall and in usability, GPT-5.6-Sol in aesthetics, and Kimi-K3 in requirement alignment. Validation reports 85.3% agreement with curated human votes on 197 arena sessions, a Spearman rho of 0.890 against the public Code Arena leaderboard, stable rankings under a substitute judge (rho 0.980), 99.89% instrumentation success, and a coverage-guidance ablation raising median function coverage from 91.9% to 94.3%. Limitations: the dataset, code, and arena-derived requirements are not released; z-scores depend on the evaluated model pool; the main judge and checklist generators are themselves evaluated models; and GPT models run under a different coding harness.

Review complete

Assessment at a glance

software engineering (LLM evaluation)

6

risk flags identified

● high 2

● medium 3

● low 1

Reproducibility readinesslow
Code & data availablenot stated
Review confidencehigh
AI text signal0/20 passages flagged
Deep research viable

4 strengths · 5 weaknesses · 5 author questions

AI text signal = Binoculars zero-shot detector score over 20 sampled passages (Fast-DetectGPT co-reported) — absence does not prove human authorship, and a flag does not imply misconduct.

Levels reflect verification complexity — not a quality score. Evolve never rates your paper.

Key claims under review

  • Separating coverage-guided exploration from criteria-based scoring avoids both crediting unreachable functionality and confounding application defects with agent execution failures.
  • WebCraftBench agrees with validated human preferences on 85.3% of 197 pairwise arena comparisons, with agreement rising as the score gap between paired applications widens.
  • Model rankings are robust to judge replacement (Spearman 0.980, 130/136 pairs preserved) and correlate strongly with the public Code Arena leaderboard (Spearman 0.890).
  • No evaluated model leads on all three dimensions; aesthetics, usability, and requirement alignment expose complementary strengths across the 17-model pool.
  • Coverage guidance raises median function coverage from 91.9% to 94.3% and cuts tasks below 90% coverage from 139 to 99 on the 360-application ablation subset.

Strengths

  • Well-motivated exploration/scoring separation

    Withholding acceptance criteria from the explorer (§4) directly addresses the checklist-teaching problem of WebGen-Bench/MiniAppBench-style setups; Table 1 positions this cleanly against 15 prior benchmarks, and §2.1 articulates why static benchmarks credit unreachable code.

  • Unusually thorough validation battery

    Human agreement (85.3% over 197 pairs, §5.3), judge swap (Spearman 0.980, §5.4), instrumentation audit with root-caused failures (99.89%, §5.5), and a coverage-guidance ablation (§5.6) — most benchmark papers in this line validate on one axis only.

  • Realistic, characterized task set

  • Transparent failure analysis

Weaknesses

  • No baseline or uncertainty for the headline agreement

  • Fully closed artifacts

  • Model-pool circularity

  • Harness and effort confound

  • Alignment ceiling effect

Full Review Report

$1.99 · one-time

Unlock the complete preliminary analysis Evolve produced for this paper.

Report preview

Scope & Claims

WebCraftBench (arXiv 2609.15387v3; Tencent Hunyuan with Tsinghua/PKU collaborators) proposes an interactive benchmark for scoring LLM-generated web applications from a software-testing perspective. Three claims structure the paper: (1) existing static and checklist-driven interactive benchmarks either credit unreachable code or confound application defects with agent failures (§1, Table 1); (2) instrumenting apps and letting a coverage-guided agent explore — with acceptance criteria withheld — yields runtime evidence that cleanly separates exploration from scoring (§4); (3) the resulting scores align with human preference (85.3% on 197 validated pairs, §5.3) and with the public Code Arena leaderboard (Spearman ρ=0.890, Fig. 1).

The remaining sections cover Methodology Assessment, Statistical Evidence, Results & Reproducibility, Limitations & Risks, and Verdict & Recommendations.

  • All 4 strengths & 5 weaknesses, analyzed in detail
  • 6 risk flags with severity, section & reviewer questions
  • Methods & statistical evidence assessment
  • 5 questions a peer reviewer would ask
  • Full six-dimension evaluation report & recommendations

One-time purchase · this paper only

One-time purchase, this paper only. AI-generated preliminary analysis — not peer review.

Frequently asked questions

What is WebCraftBench?

An interactive benchmark (369 real user requirements, 5,088 acceptance criteria) that evaluates LLM-generated web apps by automatically instrumenting them, exploring them with a coverage-guided browser agent, abstracting the interaction trace into a state-transition graph, and having LLM judges score visual aesthetics, usability, and requirement alignment from runtime evidence.

How closely does WebCraftBench match human judgment?

On 197 validated pairwise votes from an internal arena replica it agreed with humans on 85.3% of pairs (168/197). Agreement rose above 90% when the score gap between two apps exceeded 0.25 standard deviations, and its only high-margin disagreement involved preferring a working-but-plain app over a polished-but-crashing one.

Which models performed best on WebCraftBench?

Among the 17 evaluated frontier models, Claude-Opus-5 ranked first overall (+1.326 z-score) and in usability; GPT-5.6-Sol led visual aesthetics by a wide margin (+2.239); Kimi-K3 led requirement alignment (+1.283). No model led on every dimension.

Is WebCraftBench open source?

No. The authors withhold the dataset, source code, and prompts, citing data-leakage prevention and business confidentiality. This means none of its reported numbers can currently be independently verified by third parties.

About this review

This is an AI-generated preliminary review by Evolve.Pub, produced from the openly available text of the paper. It is not peer review and does not represent the authors' views. The canonical record of the paper is at the publisher link above.

  • Figures 1, 3, and 5 arrive as partially extracted text; the Fig. 1 leaderboard graphic and Fig. 4 screenshots could not be visually verified.
  • Provided metadata lists 8 authors; the full-text byline lists 12 (Tencent Hunyuan plus Tsinghua/PKU affiliates); this review follows the full-text byline.
  • Related-work characterizations in Table 1 and all citations were taken at face value, not independently verified.
  • arXiv identifier 2609.15387 and September 2026 dates are as printed in the extraction; not independently checked.

Go deeper on this paper

Reproduce ResultsNot feasible for this paper — the core results cannot be re-derived by sandboxed code simulation.

Wrote a paper? Stress-test it before reviewers do.

Upload your manuscript for the same structured scrutiny — reasoning, statistics, evidence, figures, and reproducibility.

Scan your paper
WebCraftBench: Evaluating Web Application Generation from a Software Testing Perspective | Evolve.Pub