Status-Sensitive Button Label

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

When doing a test, there are a couple of cases where the language entry 'Resume the Test' simply doesn't make sense or is incorrect. It would be ideal if these cases could have new, separate language entries.

Example 1) Test > Settings > Administering the Test: Functionality Available to Participants > Show 'List of Questions' - Show prior to the first question [box is checked].

When I now take this test with a dummy user, I have to click on 'Start the Test' - I then get the list of questions (because I checked the box for 'Show prior to the first question').... but then I get the option 'Resume the Test'... which is incorrect in English as I haven't actually started the test - so I can't resume it. Correct would be 'Proceed to Test'.

Example 2) Test > Settings > Administering the Test: Functionality Available to Participants > Show 'List of Questions' > Show before a participant finishes the test [box checked].

In this case, when having answered all the questions and clicked on 'Finish the Test' I get shown the same 'List of Questions' page, with the option (again) to 'Resume the Test'. In this case, 'Resume the Test' isn't quite as bad, but 'Return to Test' would be better.

This was submitted as a bug report on Mantis #0034889 and is related to bug report #0032629

Feedback was that changes to this behaviour are conceptual in nature and that  a feature request would be needed.

2 Conceptual Summary

'Resume Test' should only really be used when a test has been suspended or paused for some reason. Ideally the button labels should be sensitive to whether the test has already been started or has already been 'finished' but can be returned to. Current 'Resume the Test' buttons that show up before a test has been started should be labelled appropriately (for example 'Proceed to Test' or 'Return to Test').

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of 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. }

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

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: {Please add your name.}
• 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.

• …

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