| { |
| "absolute_id": 226, |
| "persona": "Backend Developer", |
| "task": "Based on the files that have not been debugged, identify the bugs in the code and generate a bug report named bug_report.txt in the debug folder on the desktop.", |
| "task_diff": "medium", |
| "output_files": [ |
| "bug report.txt" |
| ], |
| "rubrics": [ |
| "Does `bug report.txt` correctly locate and read all four source code files: `bug_file1.py`, `bug_file2.py`, `bug_file3.py`, and `bug_file4.py`?", |
| "Does `bug report.txt` completely include the three bugs identified in `bug_file1.py`: a logic error on line 23, a matching-rule error on line 23, and a logic error on line 45, with nothing omitted?", |
| "Does `bug report.txt` completely include the four bugs identified in `bug_file2.py`: a data-assignment error on line 11, a logic error on lines 18-24, a missing exception-handling issue on line 38, and a logic error on line 45, with nothing omitted?", |
| "Does `bug report.txt` completely include the three bugs identified in `bug_file3.py`: a syntax error on line 11 caused by a missing closing brace in the dictionary, a syntax error on line 59 caused by bad indentation, and the missing syringe data definition, with nothing omitted?", |
| "Does `bug report.txt` completely include the bugs identified in `bug_file4.py`, including the logic error on line 4 caused by a full-width space and the logic error on line 22 caused by iterating over `values` instead of `keys`, with nothing omitted?", |
| "Is the reversed fuzzy-matching logic bug on line 23 of `bug_file1.py` correctly identified and classified as a logic error?", |
| "Is the lack of case-insensitive matching in `bug_file1.py` correctly identified and classified as a matching-rule error?", |
| "Is the assignment of `None` to `一次性使用无菌注射器(带针)` in `bug_file2.py` correctly identified as a data-assignment error?", |
| "Is the missing closing brace in the `medical_data` dictionary in `bug_file3.py` correctly identified as a syntax error?", |
| "Is the missing indentation for the `main()` call in `bug_file3.py` correctly identified as a syntax error?", |
| "Is the incorrect iteration over `medical_data.values()` in `bug_file4.py` correctly identified as a logic error?", |
| "Does each bug entry include all five required fields: file path, line number, bug type, bug description, and consequence of the bug?", |
| "Are the three bugs identified in `bug_file1.py` arranged in ascending order by line number?", |
| "Are all bugs in `bug_file2.py`, `bug_file3.py`, and `bug_file4.py` also arranged in ascending order by line number?", |
| "Does the beginning of the report include a bug-category statistics table with the correct counts: 2 syntax errors, 7 logic errors, 2 missing exception-handling issues, 1 data-assignment error, and 1 matching-rule error, for a total of 13 bugs?", |
| "Is the report organized by file in the order `bug_file1.py` -> `bug_file2.py` -> `bug_file3.py` -> `bug_file4.py`, with clear grouping?", |
| "Does every bug include a specific, actionable fix suggestion rather than a vague description, for example changing the condition on line 23 of `bug_file1.py` to `device_name.strip() in device` and changing line 22 of `bug_file4.py` to iterate over `keys` instead of `values`?", |
| "Is the report text free of typos, punctuation errors, and awkward or unclear sentences?", |
| "Is the output file `bug report.txt` encoded in UTF-8 so that all Chinese characters display correctly?", |
| "Does the end of `bug report.txt` include a bug-category summary section that reorganizes the identified bugs by bug type?", |
| "In the `bug_file3.py` section, does `bug report.txt` explicitly point out the functional omission caused by the missing data definition for `一次性使用无菌注射器(带针)`?", |
| "At the end of each file section, does `bug report.txt` state the total number of bugs identified in that file?" |
| ], |
| "rubric_types": [ |
| "Basic Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Process Evaluation", |
| "Process Evaluation", |
| "Process Evaluation", |
| "Process Evaluation", |
| "Process Evaluation", |
| "Process Evaluation", |
| "Process Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Basic Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation", |
| "Outcome Evaluation" |
| ], |
| "file_dep_graph": [ |
| { |
| "from": "bug_file1.py", |
| "to": "bug report.txt" |
| }, |
| { |
| "from": "bug_file4.py", |
| "to": "bug report.txt" |
| }, |
| { |
| "from": "bug_file2.py", |
| "to": "bug report.txt" |
| }, |
| { |
| "from": "bug_file3.py", |
| "to": "bug report.txt" |
| } |
| ], |
| "data_manifest": [ |
| { |
| "filename": "bug_file1.py", |
| "stored_relpath": "data/211a8cda565cc32c_bug_file1.py" |
| }, |
| { |
| "filename": "bug_file4.py", |
| "stored_relpath": "data/3c6de63416388a60_bug_file4.py" |
| }, |
| { |
| "filename": "bug_file2.py", |
| "stored_relpath": "data/c7d3cc7e5ac74ba8_bug_file2.py" |
| }, |
| { |
| "filename": "bug_file3.py", |
| "stored_relpath": "data/6ac134343d53d690_bug_file3.py" |
| } |
| ], |
| "tested_capabilities": [ |
| "Result-Providing Files Utilization", |
| "Semantic Content Relations Understanding" |
| ] |
| } |
|
|
