Test in editor
How staff try a programming problem in the same code editor students use – its published or unpublished version – and why it never counts in a course.
Test in editor opens the code editor students use, outside any course. Use it to check that the statement is clear, the tests are right and the limits fit before you give the problem to students. The address is /library/problems/<problem>/try.
Where to find it
Section titled “Where to find it”- At the top of the problem page and the tests page – Test in editor. When the newest version isn’t published yet and you can edit the problem, the unpublished version opens.
- The ⋯ row menu in the problem archive → Test in editor – the published version.
- The row menu of a course’s problem list – the published version.
The editor opens in a tab of its own. Excel tasks have no code editor; for them the page says This problem cannot be tested in the editor.
Which version, and who may
Section titled “Which version, and who may”| Version | Who can test it | Address |
|---|---|---|
| Published (the newest) | Everyone who sees the problem in the archive: teachers, course staff, group and organisation admins, system administrators | …/try |
| Unpublished | Only people who can edit the problem | …/try?version=draft |
Students never reach this page. When a problem has never been published, its editors get the unpublished version.
The editor header says what is being tested: Testing version N or Testing version N · not published. The link beside it, Test the unpublished version or Test the published version, switches versions.
staff/library/test-in-editorWhat you can do
Section titled “What you can do”Everything works as in a student’s editor: choosing a language, Run samples, Run with custom input and Submit. The differences:
- Languages – the version’s own languages, or every enabled language when it has none (there is no course to narrow them).
- Starter code – only the problem’s own; course templates are not used.
- Limits – no daily attempt limit and no topic window. Your general limits, shared with your course work, apply: at most 3 submissions judged at once, 6 submissions and 12 runs per minute.
- Code drafts in the browser are kept apart from your code in courses.
The code editor and runs are described in the students’ pages Code editor and Running and submitting.
What you see in the results
Section titled “What you see in the results”- A submission is judged on every test of the version.
- You see every test’s row, the first failed test and the compiler messages.
- You see hidden test data only when you can edit the problem; otherwise the list says “Hidden test data is shown only to the problem’s editors.” Sample test data is visible to everyone.
- You see only your own attempts. Results arrive by themselves, with no need to reload.
Tests never count in a course
Section titled “Tests never count in a course”These submissions belong to no course. They don’t appear in courses’ submission lists, progress, grades, the progress sheet, activity, the home page, similarity checks or exports. The inbox doesn’t notify you about their results. Students never see them.
| Testing the unpublished version | Testing the published version | |
|---|---|---|
| Is it kept | Deleted when the unpublished version’s tests change, it is published or the problem is deleted. | Kept like any submission. |
| Does it block deleting the problem | No. | Yes: a problem with such a submission can only be archived. |