search

tiffanyliu0220 / pe

0 stars 0 forks source link

The Input difference for the "results" command and other commands #6

Open tiffanyliu0220 opened 2 months ago

tiffanyliu0220 commented 2 months ago

For "results" command, we're able to input results with extra letters after "results" but why aren't we able to do so for other commands? What is the purpose for this then? And why is it especially just for the "results" command? Is there any significance for results?

soc-se-bot commented 2 months ago

Team's Response

This was intended for easier usage (better recognition) of the results command. While it could have been similarly applied to other commands, we believe this issue is framed as a suggestion. It is not a critical functionality of the product and the current design does not cause inconvenience to the users.

As quoted from the textbook regarding suggestions:

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The inconsistency of the input format confuses the users when keying in their inputs for other commands. They may forget which command is allowed to add additional extra characters behind the main command, which is not allowed to. Not only that, as "results" command is the only command that allows for extra characters at the back, gradually when they key in inputs for other commands, they will forget about this additional feature that "results" have. In that case, would this additional feature of the "results" command be rendered as redundant? That's why I asked what is the purpose of this so that the app is able to make full use of this additional feature that "results" command and only this command has.

I agree that the current command indeed doesn't cause inconvenience to the users, just that considering the significance of this command's additional feature, I don't think it creates a value in this case.