Ui display errors to user.

[muserr]

Why does the program show no viable alternative?

What am I supposed to do? I can only make it for that cca timing.
This message should not be displayed to users.

[nus-pe-bot]

Team's Response

The time format as specified in both the app and the User Guide has not been followed, as some extra spaces has been injected into the times.

Rejecting this as a bug.

This would instead be added into the list of expected anomalous beheavior as it is acknowledged that not strictly adhering to 24 hour format may result in anomalous behavior.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: I would like to thank the developers for their response.
However, the developers response failed to address the issue stated.

I respectfully disagree with the developer's response for the following reasons:

Kindly note, as seen from the original comment from tester: "Why does the program show no viable alternative?"
I am questioning the need to display statements such as:

The above are Natty errors that are displayed to user which was definitely not included as part of the Developer's response for "Expected Anomalous Behavior":

(Taken from the team's UserGuide, pg 19)

Furthermore, if we look at the UserGuide:

(Taken from the team's UserGuide, pg 1)

And under 4.1 Parser Errors:

(Taken from the team's UserGuide, pg 15)

There was no mention that 'natty' related errors will be displayed to users.

From a user's perspective, I'm trying to answer questions such as "so what does this mean for the user" and in this context: "how can the user benefit from the program's user interaction".

However, I could not find a good answer for the need to display the abovementioned stack trace errors to the user.

The natty error messages certainly does not tell the user that: "some extra spaces has been injected into the times" as stated in the developer's response.

Displaying these error messages certainly won't help the users have a better understanding of what went wrong in their use of the feature itself or how they can go about rectifying the issue.
This is therefore a bug.

---