Updating Questions in running Random Tests

1 Initial Problem

Test questions can no longer be synchronized with the Question Pool as participant data becomes available. This behavior is necessary to be able to compare the test results.
If ILIAS users work with a Test with the setting Random Set of Questions that selects a small number of questions from a large Question Pool, the Test Results are  only marginally comparable. However, the Test Questions can no longer be synchronized in a Random Test as participant data becomes available.
If users update and expand the question pool on a regular basis, the questions can not be transferred into the Ramdom Test
The user have to create a new Test with the setting Random Set of Questions after each change in the Question Pool.

Since the Test Results are not transferable or consistent, this results in a unmanageable amount of random Random Tests.

2 Conceptual Summary

When a user activates the radio button "Random set of questions", the following options should be offered to him:

• Questions can be updated in running tests
  • Changes and new questions can be synchronized after the start of a Random Test or the availability of participant data. This setting is not suitable for e-exams.

• Questions can not be changed/updated in running tests
  • Questions can no longer be changed and synchronized from a Question Pool as soon as participant data is available. Suitable for e-ecam.

3 User Interface Modifications

3.1 List of Affected Views

• Test>>Setting>>Random Set of Questions
• Test>>Questions

3.2 User Interface Details

Mockups

3.3 New User Interface Concepts

None.

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: Zenzen, Enrico [ezenzen]
• Maintainer: Heyser, Björn [bheyser]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

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

• …

7 Discussion

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