Waiting time should only be enforced if the test pass is failed

1 Initial Problem

A test can be performed several times. The best test pass scores. Users should be able to view their answers after each test run to learn why they failed the test.

Waiting time should only be enforced if the test pass is failed. Users who have passed the test and want to continue learning/practicing with the test OR want to improve their test score (best test pass scores.) Should not have to wait between test passes.

2 Conceptual Summary

OPTION 1

If the described use case is generally valid and can be transferred to many scenarios, the setting could be adapted accordingly and the waiting time would ONLY affect users who have not passed the test.

OPTION 2

If the setting cannot be changed, an additional sub-setting is to be introduced. The setting is displayed as a radio button below Force Waiting Time between Passes.

• By default, the radio button 'Force wait time between all Passes' is selected.
• If users select the radio button 'Force waiting time only between failed Passes', the waiting time only applies to users who have not passed the test.
• If users select the radio button 'Force waiting time if test passed', the waiting time only applies to users who have passed the test.

3 User Interface Modifications

3.1 List of Affected Views

• Test > Settings > Force Waiting Time between Passes
• Force Waiting Time between Passes

3.2 User Interface Details

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ 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

{ 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: Zenzen, Enrico [ezenzen]
• Maintainer: Strassner, Denis [dstrassner]
• 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.

• …

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