Feature Wiki

Information about planned and released features

Tabs

Test Question Interface

1 Initial Problem

Test questions are bound to the question pool and test object and have many dependencies to their methods. There is one exception in learning modules but this implementation is located in the SCORM learning module and does not allow the use of plugin questions. The main goal of this feature request is to allow a wider use of test questions. In partiular:

  • Make questions usable outside tests
–Plugin question in learning modules
–Offline Exams and
–Flashcards, InteractiveVideo, App
  • Keep question handling in question
–Migrate current implementation in LM
–Cut dependencies from test and pool
–First step toward question service
  • Support offline and online
–Define PHP and Javascript Interface
–Respect capabilities of question and context

To achieve this goal, a Test Question Interface is defined that can be implemented by questions and used by player contexts.

2 Conceptual Summary

The specification is part of a concept for offline exams and can also be used to implement a page component plugin that allows the integration of plugged test questions on ILIAS pages. It is currently available in German only but can be translated when a stakeholder for this feature request is found.

3 User Interface Modifications

No user interface changes are planned for the presentation of questions. Just a refactoring of their presentation functions.

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, 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 Contact

  • Author of the Request: Neumann, Fred [fneumann]
  • 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.}

6 Funding

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

7 Discussion

Neumann, Fred [fneumann], 6.3.2019
Withdrawn in favour of Offline-Support for Test Questions

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

Last edited: 9. Mar 2022, 13:32, Kergomard, Stephan [skergomard]