Is your feature request related to a problem? Please describe.
Currently, tags are a feature mainly unused. One of the three tag type has been recently reverted (see https://github.com/UCL-INGI/INGInious/pull/855). However, its ability to mark verification steps in the grading process of the task's run file is still valuable.
Indeed, the feedback is mainly returned as textual, human-readable, data which is not really usable in automated task testing.
Also, providing multilingual feedback is not possible.
Describe the solution you'd like
The idea is to decouple the task feedback from the grading process. Tags mark the various steps of the evaluation (e.g. code compilation, code returned a segfault, ...). The textual feedback is then returned according to the tags values and in the preferred language of the user. Such tags are then used by the automated tester to ensure the consistency of the grader behavior on a same submission.
Additional context
The tags values should not appear anymore on the interface since the textual feedbacks are their user-friendly reflect.
Statistical analysis based on tags is still possible.
Is your feature request related to a problem? Please describe. Currently, tags are a feature mainly unused. One of the three tag type has been recently reverted (see https://github.com/UCL-INGI/INGInious/pull/855). However, its ability to mark verification steps in the grading process of the task's run file is still valuable. Indeed, the feedback is mainly returned as textual, human-readable, data which is not really usable in automated task testing. Also, providing multilingual feedback is not possible.
Describe the solution you'd like The idea is to decouple the task feedback from the grading process. Tags mark the various steps of the evaluation (e.g. code compilation, code returned a segfault, ...). The textual feedback is then returned according to the tags values and in the preferred language of the user. Such tags are then used by the automated tester to ensure the consistency of the grader behavior on a same submission.
Additional context The tags values should not appear anymore on the interface since the textual feedbacks are their user-friendly reflect. Statistical analysis based on tags is still possible.