Thanks for reporting back. Good to know it's solved. The fact that the Moodle xml question importer can't handle windows line breaks does sound like a bug, as XML is defined to accept either line break format. But I doubt it's worth reporting it as a bug, as the developers can reasonably argue that their particular variant of a Moodle XML question import is intended only for use in an export -> import sequence, for which it works just fine.
CodeRunner does not display long strings in test result expected/got columns in the result table. They are 'snipped' to a maximum length of 8k characters by removing the middle bit and replacing it with the string "...snip...". So there shouldn't be a significant performance problem from the student's perspective. But it does slow down the editing of a question for the teacher.
The stdin/expected/got fields of a test case are not really intended for large scale test data. I recommend using support files for such situations rather than using stdin. And it's best to avoid displaying large test expected and/or got data to the student.
For my in-house program contest question type I replace large test data Input/Expected/Got data with links, but they're just data URIs, so the complete data is still encoded within them. The latest version of CodeRunner does allow combinator graders to return links to temporary feedback files so you could use that approach, with a few caveats that are explained in the documentation.
CodeRunner does not display long strings in test result expected/got columns in the result table. They are 'snipped' to a maximum length of 8k characters by removing the middle bit and replacing it with the string "...snip...". So there shouldn't be a significant performance problem from the student's perspective. But it does slow down the editing of a question for the teacher.
The stdin/expected/got fields of a test case are not really intended for large scale test data. I recommend using support files for such situations rather than using stdin. And it's best to avoid displaying large test expected and/or got data to the student.
For my in-house program contest question type I replace large test data Input/Expected/Got data with links, but they're just data URIs, so the complete data is still encoded within them. The latest version of CodeRunner does allow combinator graders to return links to temporary feedback files so you could use that approach, with a few caveats that are explained in the documentation.