Open jannaleong opened 4 months ago
Thank you for pointing this out. As the current version is not incorrect and does not crash the app, we will put it in NotInScope. Nevertheless, this is a useful enhancement for future iterations, so thank you.
Team chose [response.NotInScope
]
Reason for disagreement: I believe the team has not fully comprehended the nature of my bug.
I take issue with the specificity of the error message.
As seen in the screenshot below, if an error message is not specific enough, it can be counted as a feature flaw. The tp guide even provides an example saying how calling an invalid value(in this case an empty value for the con field) a format error(which is reflected by their error message saying "invalid command format"), is a severity low bug.
With the bug reported almost exactly matching the example given in the tp guideline, this is a feature flaw of low severity.
input : find con/ output : invalid command format exception message
I expected to receive a more specific error message telling me that i have entered an empty value for con field. However, I only receive a general errror message saying i have invalid command format.
This is problematic as users will be confused as to which part of the command they have entered incorrectedly. This is not optimised for fast typist they can easily miss out a field.