Test Player « Preconditional Test »

This feature request is part of the project Splitting-up T&A Into New Components.

1 Initial Problem

Currently sometimes Tests in ILIAS are used to present testees some explanations and regulations. The Question texts give the information, an using some type of multiple choice (like somle yes/no)  testees give the information that they understood the information or accept the reguatioins presented.
The test is only passed, if every question ist answered correctly, and the status "passed" then is used as a precondition for the access to other objects in ILIAS.

Testruns are used to document user's reception of information or their consent

Some possible examples for the use of these tests are:

• prior to starting an exam, users are presented exam reguations, and the single question in this test is "(... this are the regulations for this exam...), and "Did you understand all these regulations and accept them"?. Only after answering "yes" the exam is presented to the users.
• prior to access a datacollection that allows to "book" courses that require payments, the tests gives instructions how to use the datacollection and presents the terms and conditions and privacy regulations. in two or three questions users are asked if they understood the instructions and accept the terms

2 Conceptual Summary

Details of the requirements were discussed in the working group Splitting up... and are stored in Vorschalttest.

Some special settings are highlighted here:

• no randomized questions
• few information before starting test required
• no password/ selected participants/ limitations on counts required
• no max count on testruns or time restrictions
• since all questions have to be answered "correctly", no numeric scores for questios are required or should be presented
• randomized order of questions is not wanted
• no feedback while performing a testrun is required
• all questions have to be answered, and concepts like "partially correct" are not applicable
• since we have a documentation-purpose bases on timestamps, last run always counts and testruns must not be deleted
• participants must have access to their results, but only after finishing runs. Most Details to testruns are not applicable

3 User Interface Modifications

3.1 List of Affected Views

This is to be discussed after a general discussion of testplayers

3.2 User Interface Details

see 3.1

3.3 New User Interface Concepts

none (for now)

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

As in all tests it is needed to store user's individual test data like user-id, test date and of course answers given (probably including a history)

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: Jackisch, Ingo [jackisch]
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• DHBW

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