search

michaeldinata / pe

0 stars 0 forks source link

add command does not allow trailing space, but allows leading spaces #4

Open michaeldinata opened 4 years ago

michaeldinata commented 4 years ago

Screenshot 2020-11-13 at 16.43.28.png

Similar to the taking in of parameters, but this is the other way round, and is regarding the command type itself

nus-pe-bot commented 4 years ago

Team's Response

Thank you for your response. We do not believe this to be a bug as it is stated within the UG that each space separated description corresponds to the expected argument.

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Thank you for the response. I feel that the team had sadly not answered the feedback properly because their response did not address why trailing spaces are not allowed and why leading spaces are allowed. As mentioned in another bug response, the UG did not state that each space separated description correspond to the expected argument, but does mention how each word in the description corresponds to the expected argument (as seen in the image the team gave).

Also, as compared to the other similar bug report, that bug allowed trailing spaces but not leading spaces, while this bug allowed leading spaces instead, and do not allow trailing spaces.

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: As a fast-typer, a user may sometimes accidentally press the spacebar more than one time. This would cause inconveniency and confusion because if the user had pressed the spacebar before the description, then his command is not allowed, but if the pressed it after the description, then the command is allowed.