search

Barbaracwx / pe

0 stars 0 forks source link

Unhelpful/strange error handling messge #8

Open Barbaracwx opened 10 months ago

Barbaracwx commented 10 months ago

In the UG, the error handling message for an invalid command should be "Invalid command! Please try again.".

However, when I type in some invalid commands, the error message it returns shows a different invalid command message.

image.png

nus-se-script commented 9 months ago

Team's Response

It's not a functionality bug. I think it would go as an documentation bug as the invalid message is displayed. The problem is that there is an added message

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: While I understand the perspective that this issue might seem like a documentation bug as it pertains to error message content, it's crucial to recognize the impact it has on user experience. The issue here isn't solely about the documented error message but about the inconsistency in the feedback presented to users upon encountering an invalid command.

Consistency in error messaging is fundamental for user understanding and system predictability. Users rely on consistent error messages to comprehend what went wrong and how to rectify it. In this case, the discrepancy between the expected error message and the actual message returned introduces confusion.

This inconsistency poses a risk of user confusion and might lead to unnecessary troubleshooting efforts. Users expect clear and consistent communication, especially when encountering errors. Any deviation from the expected response could potentially erode user trust in the system's reliability and raise concerns about its integrity.

Additionally, considering this discrepancy as merely a documentation issue overlooks the fact that the displayed error message is an essential part of the user interface. Even if the discrepancy is minor in content, it reflects a deviation from the established standards and can impact the overall user experience negatively.

Addressing this issue isn't merely about correcting a documented message; it's about ensuring a coherent and predictable user interaction with the system. Therefore, categorizing it as a functional bug aimed at maintaining consistent user feedback aligns more accurately with the importance of preserving a seamless user experience.