pranav-ganesh / pe

0 stars 0 forks source link

Error message bug 3 #8

Open pranav-ganesh opened 2 years ago

pranav-ganesh commented 2 years ago

image.png

This confused me initially since I thought the command was correct but the error message says 'unknown command', giving the false impression that an add command doesn't exist. A more appropriate message would be to say invalid command format and give the correct command format

nus-pe-bot commented 2 years ago

Team's Response

The command you entered is add-ccn/John which is an unknown command

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Error message bug

image.png

As a user when I enter tab1 instead of tab 1, I expect an error message that shows invalid command format and displays the correct command format. I feel this error message is inappropriate


[original: nus-cs2103-AY2122S1/pe-interim#5847] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

The product is not missing a critical functionality that makes the application less useful for users. The team decided to follow standard command line conventions as shown below

image.png

image.png

image.png

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]


:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I would expect the application to parse the first few characters of the command to get an indication of which command the user is trying to execute and then throw an error message accordingly. While I agree that the team's application works correctly, it is not optimized to recognise which command a user is trying to type and throw an invalid command format error for that specific command instead of a generic unknown command.

When the user enters tab1 instead of tab 1, he/she would expect the app to throw an invalid command format error message for the tab command along with the correct format to use rather than an unknown command message. This is not a functionality flaw but rather a feature flaw.

Therefore, this can be classified as a bug with low severity.