Automatical update of remaining test time after adding extra time for users

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Due to https://mantis.ilias.de/view.php?id=28577

As of today, test participants need to navigate within a test (i.e. send an answer to a question to the server or go back and forth between questions using the tests navigation menu), in order to update the client side of the test working time. The working time for the test is not updated on a regular intervall. User interaction is required.

This poses a problem when tutors/teachers give extra time close before the end of the working time is reached.

2 Conceptual Summary

Extra time needs to be synched with participants clients working on the test on a regular intervall. The synchronization must not need user interaction.

- test (players) should check for updates to extra time on a regular intervall during the working time of the test
- in case automatic saving is active this feature could also update the working time in order to keep server requests at a minimum
- in case the client side end of working time is reached, the test must make one final request to check if additional extra time has been awarded in the meantime and if so, not finish the test, but update the working time accordingly

3 User Interface Modifications

• tbd

3.1 List of Affected Views

• tbd

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, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

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 Privacy Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Sesterhenn, Fabian [sesterhenn]
• Maintainer: Becker, Maximilian [mbecker]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• TH Köln

9 Discussion

10 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}.