Datasets:
File size: 2,256 Bytes
fbb6c7b |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
---
license: cc-by-nc-4.0
tags:
- mlcroissant
configs:
- config_name: default
data_files:
- split: CoreCodeBench_Multi
path: CoreCodeBench_Multi.jsonl
- split: CoreCodeBench_Difficult
path: CoreCodeBench_Difficult.jsonl
---
# Multi Testcases for CoreCodeBench
## File Explanation
+ `CoreCodeBench_Multi.jsonl` Multi test cases for CoreCodeBench.
+ `CoreCodeBench_Difficult.jsonl` More difficult version for CoreCodeBench multi test cases .
## Key Explanation
| Key | Meaning/Description |
| ------------------ | ------------------------------------------------------------ |
| **id** | A list of unique identifiers for the functions to be completed, typically in the format `module.path.Class::function`. |
| **project** | The name of the project this data is associated with. |
| **origin_file** | A list of file paths indicating where each function or method is defined in the source code. |
| **test_list** | A list of file paths for test scripts that are related to or used for testing the functions/methods. |
| **prob_info** | A list of dictionaries, each containing detailed information about a function or method, such as its starting and ending line numbers, and the actual code (`func_code`). Each dictionary includes: `class_start_lineno`/`class_end_lineno`: Line numbers where the class begins and ends. `func_start_lineno`/`func_end_lineno`: Line numbers where the function begins and ends. `func_code`: The source code of the function as a string. |
| **type** | A list indicating the type or category of the functions/methods (e.g., "function_empty"). |
| **node** | A list of fully qualified names (with module and class) for each function/method. |
| **language** | The programming language used. |
| **toolfunc_count** | The number of tool-related functions in the data. |
| **func_count** | The total number of atomic functions in the data. |
| **pytest_info** | A dictionary with information about pytest test results: `total_num` is the total number of unit tests, while `base_passed_num` is the number of base tests that passed. |
|