Extending Continuous Testing Mode: Consider Processing Time

1 Initial Problem

By now (version 5.2), the Continuous Testing Mode (CTM) is only judging the success in processing a question by means of the achieved scores.
However, in the scenario of exam preparation also the time needed for solving a question is relevant, as exams usually feature a restricted amount of time for a participant. So, it is of great interest for an examinee whether he/she solved a question in an acceptable time.

2 Conceptual Summary

So, my proposal is to enhance the settings of the CTM (or its selection options) by a "purgatory" status for questions (separate article) and to add as one possible trigger for this status that a question has been solved but only at the price of wasting too much time.

The "Processing Time" property of questions could be used to indicate to participants whether they are "fast enough" to pass the exam.

ILIAS test questions already feature a "Processing Time" property, however, currently it isn't really used as tests do not anymore add the amounts of single questions' time into a proposal for an overall test processing time – since ILIAS 5.0 ILIAS always suggests 90 minutes.
Currently, there's a feature request on this topic: Limited Question Working Time.

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]; Wischniak, Stanislav [wischniak]
• Maintainer: Heyser, Björn [bheyser]
• Implementation of the feature is done by: Databay AG

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• ...

7 Discussion

Kergomard, Stephan [skergomard], 2022 Mar 9: We close this as part of the cleaning up effort undertaken in the Splitting-Up Test & Assessment Workinggroup.

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.