search

pranav-ganesh / pe

0 stars 0 forks source link

Case sensitivity bug #10

Open pranav-ganesh opened 2 years ago

pranav-ganesh commented 2 years ago

image.png

When the command is ADD instead of add, there is an unknown command error thrown. I don't see any reason why the commands can't be case insensitive. Even if it is case sensitive, I believe the error message should be invalid command format for the add command and not unknown command

nus-pe-bot commented 2 years ago

Team's Response

This is a minor issue and does not affect the main purpose of the application.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: I don't agree with the team's justification and believe that their line of argument is too weak. When the user enters the command name as ADD-c instead of add-c, he/she would expect one of the following responses from the application:

(1) The command works as desired if the command name is case insensitive

(2) If the command is case sensitive, then there should be an error message saying invalid command format and the correct command format for the add-c command should be reflected. The current error message ('Unknown command') is irrelevant and inappropriate given the fact that the UG doesn't explicitly share about the case sensitivity of the command names

Therefore, this should be a bug of low severity.