Though the revision history is useful to some extent, it would be more useful if the history also showed detailed test results (i.e. the output we get when we run the spec test as an assistant).

Current workaround: Use our test account to copy/paste the submission there and see what the test results are.
Use case: Student has posted a discussion item, but since then refactored it’s code dramatically or started a new approach, but still wants the discussion post answered.

Submitted by Algoritmiek-TAs on 20 November 2015 at 10:00

Rather, you want to select a revision and then apply tests to it.

Well that’s not what I meant, but I guess rerunning might be good enough…
It would be even better if results are just saved.

Added test results (n/m tests passed) to revision history for revs where spec-tests were executed. Clicking the revision will also show the failure details to observers/managers, not to students.