soc-pe-bot
commented
5 months ago Team's Response
UG has stated the correct format for all commands, and to follow it strictly or errors will be thrown. This is expected behaviour.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I understand that the current behavior of our application when encountering an invalid command is to display an "invalid command" message. However, I've noticed that this approach is too ambiguous and doesn't align with the more informative exception handling present in other areas of the program. When an exception is caught elsewhere, the application typically provides the correct command format, which is incredibly helpful for users to understand and correct their mistakes. I expect this level of detailed feedback to be consistent throughout the application. Clear and instructive error messages are crucial for a positive user experience, as they not only communicate the nature of the error but also guide users toward the correct input format, thereby preventing repeat errors and facilitating a smoother interaction with our system.
The adding a run command correctly parses command when there is a space between the "workout" and the first attribute. But when the space is removed a ambiguous error is displayed without clear indication of what caused the error.