-
Notifications
You must be signed in to change notification settings - Fork 29
Description
Hi @arkirchner,
as discussed, we would like to improve the error messages that students are getting from CodeOcean atm.
We identified multiple options, that we thin could be improved/restructured. I'll list them here and depending on what you find out to be most suitable/feasible, we can open more smaller issues.

-
In this example we would like to sort the tests not by order of files but by which tests failed and which didn't. Here, Test-Datei 2 and Test-Datei 3 should be the two topmost. And the green ones should be collapsed. Meaning all info (Erfolgreiche Tests, Punktzahl, Feedback, Fehlermeldungen) can be extended but are not shown to begin with.
-
Title should be more self explanatory. At the moment they refer to files which the user cannot see. For a user it would be more helpful to either have a clear reference to the file which threw the error or maybe directly a reference to the type of error, here e.g. (Problem mit der Methoder sayAge())
-
If possible if would be amazing to even refer to the problematic line in the code under test.

-
The full stack trace should either be collapsed to begin with and/or be prefiltered. It mostly contains information related to files that the user cannot see so it doesn't add any benefit to the user
-
This is more of an optional thing, but if it would be an option it would also be cool to be able to show the exact test case that failed. This might be too much for beginner courses but for more advanced learners seeing the test case might help to understand why it fails.

- Again this is an optional thing as well, but in futurecoder.io there is a very extensive example which also shows which values the variables had at the point of failure.
Thanks a lot and looking forward to hear what is possible.