search

m1oojv / pe

0 stars 0 forks source link

unhelpful error message from nok #18

Open m1oojv opened 10 months ago

m1oojv commented 10 months ago

Screenshot 2023-11-17 at 5.04.47 PM.png

does not give explanation of examples of valid

soc-pe-bot commented 10 months ago

Team's Response

Thank you for pointing it out. Please refer to point 3 of our Planned enhancements in the DG:

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: While I appreciate the planned enhancements to provide more specific error messages, I must insist that the current issue extends beyond just the specificity of the error messages. The core of the issue lies in the absence of example commands in the error feedback, which is crucial for guiding users, especially when they encounter an error.

  1. Importance of Actionable Feedback: When users encounter errors, especially those new to the application or unfamiliar with certain commands, they often rely on the error message to guide their next steps. An error message that lacks an example of a valid command fails to provide actionable feedback, leaving users uncertain about how to correct their mistake.

  2. Consistency Across Commands: It appears that other commands in the application do provide example commands when an invalid format is encountered. This inconsistency in user support between different commands can lead to a disjointed user experience. Users may expect similar helpful guidance across all commands, and the lack of it in some cases could lead to frustration and a steeper learning curve.

In fact almost all the other commands in the application provides example commands after the error message of invalid command. Therefore, in the context of consistency as well, this should be an issue that no example commands were given and thus inconsistent with the rest of the command error messages.

Screenshot 2023-11-22 at 11.14.12 AM.png

  1. Enhancing User Autonomy: Providing example commands in error messages empowers users to independently rectify their mistakes without needing to consult external resources frequently. This is particularly important in a fast-paced environment like a hospital, where efficiency and quick problem-solving are essential.

  2. Comprehensive User Support: The objective of any user guide or error feedback system should be to offer comprehensive support. This includes not only explaining what the error is but also demonstrating how to fix it. By providing example commands, the application can ensure that users are adequately supported in using it effectively.

Given these considerations, the lack of example commands in the error messages for the 'nok' command and possibly others is a significant oversight that affects the application's usability. I must emphasize that your planned enhancements seems only limited to providing better and more specific error messages and not including example commands that will aid the user, especially your non tech savvy target users , head nurses.

Screenshot 2023-11-22 at 11.17.53 AM.png

Additionally, I'd like to highlight the guidance provided by the professor regarding the handling of bugs. A rejection of a bug should be reserved for cases where the bug is deemed irrelevant or unnecessary to address, both in the current context and in the foreseeable future. However, in this instance, the issue at hand is directly relevant and necessary to address. The absence of example commands in error messages is a significant usability concern, especially for users who are not deeply familiar with the application's command structure. This is not a minor or irrelevant detail; it's a fundamental aspect of user support and interface design that directly impacts the ease with which users can navigate and effectively use the application.

Given the application's target audience of head nurses and other healthcare professionals, who may not have extensive technical expertise, clear and instructive error messages are essential. These users rely on the application for critical tasks and need to be able to quickly understand and rectify errors as they do not have a lot of time to fiddle with your application while on duty. The current lack of examples in certain error messages impedes this process, potentially leading to frustration and inefficiency, which are particularly problematic in a healthcare setting. Considering this perspective, the issue should not be dismissed as inconsequential or irrelevant. Instead, it should be acknowledged as a genuine area for improvement, in line with the goal of enhancing user experience and interface intuitiveness.