Measure Working Time on Test Questions

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

The test statistics do not include information on the working time for specific questions within a test, only the test overall.

2 Conceptual Summary

ILIAS should track / measure the working time per question and participant and report these times in the test statistics.

3 User Interface Modifications

3.1 List of Affected Views

Test Statistics:

• TEST / Statistics
• TEST / Statistics / Evaluation for all Users
• TEST / Statistics / Aggregated Test Results
• TEST / Statistics / Results by Question

• TEST / Results / All Participants / TEST RESULTS FOR PARTICIPANT / Detailed Results
• TEST / Results / Test Results / Detailed Results

3.2 User Interface Details

3.2.1 TEST / Statistics / Evaluation for all Users

• Add column Question Working Time for average working time per question

3.2.2 TEST / Statistics / Aggregated Test Results

• Add column Working Time to table Average Points
• Add column Working Time to evaluation export data (.xls and .csv)

3.2.3 TEST / Statistics / Results by Question

• Add column Working Time for average working time to table Questions Answered in this Test

3.2.4 TEST / Results / All Participants / TEST RESULTS FOR PARTICIPANT / Detailed Results

• Add column Working Time to table Detailed Overview for Pass N
• Add column Working Time to table Detailed Overview for Pass N to PDF export data

3.2.5 TEST / Results / Test Results / Detailed Results

• Add column Working Time to table Detailed Overview for Pass N
• Add column Working Time to table Detailed Overview for Pass N to PDF export data

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

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 Privacy

• Working Time per question per test participant

6 Security

No change required.

7 Contact

• Author of the Request: Sesterhenn, Fabian [sesterhenn]
  
• 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.

• TH Köln
• Universität Bonn

9 Discussion

Rabah, Rachid [rabah], 12 OKT 2021: I support the idea and had a similar FR, see  https://docu.ilias.de/goto_docu_wiki_wpage_6063_1357.html

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