引導式測驗 · 中等 等級

SWE-bench 和 Coding Agent 基準測驗

測試 SWE 基準任務的建構方式、FAIL_TO_PASS 和 PASS_TO_PASS 評分、Lite 和 Verified 子集,以及腳手架更改結果的原因。

問題 1 的 8

SWE-bench 任務要求系統做什麼?

預覽每個問題8 問題

當您參加測驗時,就會出現答案和解釋。

  1. SWE-bench 任務要求系統做什麼?
    • Write a new library from a specification
    • Produce a patch that resolves a real GitHub issue in a Python repository
    • Answer multiple-choice questions about code
    • Translate code from Python to Java
  2. 什麼是 FAIL_TO_PASS 測試?
    • Tests that always fail
    • Tests the agent writes itself
    • Tests that are skipped during scoring
    • Tests that failed before the human fix and passed after it
  3. PASS_TO_PASS 測試的功能是什麼?
    • Checking that the patch did not break behavior that already worked
    • Checking the code style of the patch
    • Measuring how fast the patch runs
    • Verifying the issue text is accurate
  4. 什麼是 SWE-bench 驗證?
    • The full set of 2,294 tasks
    • A set of JavaScript tasks with screenshots
    • 500 tasks screened by human engineers to remove vague issues and unfair tests
    • A private test set never released publicly
  5. SWE-bench Lite 中有多少個實例?
    • 164
    • 300
    • 500
    • 2,294
  6. Why can the same model get very different SWE-bench scores?
    • Scores depend on the scaffold that lets the model browse, run commands and edit files
    • The tests are randomly generated each run
    • The repositories are different for each model
    • Only the model's size affects the score
  7. Which is a real limitation of the original SWE-bench?
    • It has no tests
    • It uses only synthetic issues
    • It cannot be run in Docker
    • It is Python-only and drawn from about a dozen repositories
  8. Does the agent see the evaluation test patch while working?
    • Yes, it is included in the issue text
    • Yes, but only the PASS_TO_PASS tests
    • No, the harness applies the test patch separately after the agent's patch
    • No, because SWE-bench has no tests