Improved look of page Test Results

1 Initial Problem

The current page for displaying the user's test results in a test looks very technical and not attractive for users. This is a pity because this page is very important to motify a learner. I am sure we could improve this view.

2 Conceptual Summary

The already existing Kitchen Sink UI element 'Presentation Table' could be used to restructure the presentation of data on the test results page and beautify its appearance. Each row will contain the data of one test run, showing the latest pass always on top followed by earlier one (numbered). Position of existing data should be as follows:

• Title: Latest Pass | Pass # (the latest pass should not numbered but explicitly called "Latest Pass"
• Subtitle (only used when results are viewed from a tutor and not from learner, in this case this info makes sense): User name
• Selected data (shown when akkordeon is collapsed):
  • 'Date' (date of pass)
  • 'Scored Pass' (in case it is the scored one, otherwise nothing)
  • 'Percentage' (percentage solved)
• Main data (shown when akkordeon is expanded) - left side:
  • Date of Pass: DD.MMM.YYYY, HH:MM
  • Rating: Scored Pass ('last past scored' | 'best pass scored') | Ignored for Scoring
  • Answered Questions: x of y
  • Points: n of m
• Main data - right side:
  • Percentage presented as UI 'Progress Meter'
  • Button 'Detailed Results'

3 User Interface Modifications

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: Kunkel, Matthias [mkunkel]
• 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.

• ILIAS-Verein

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