nus-pe-bot
commented
3 years ago Team's Response
Our v1.4 product has not yet catered to the use of wrong commands to prompt the correct related commands, maybe this function will be updated in v2.0 instead.
Type is changed to FeatureFlaw as this is an enhancement to the features delivered in v1.4
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue type
Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
No details provided.
Step: type any command with a capital letter at the start.
An expected user behavior, especially for a fast typer could be typing in a case-insensitive way. Granted, this is not an accepted command, but the parser should be able to at least direct the user to a similar command. For instance if I use "Find" instead of find, I do expect the system to be able to direct me to the find command, instead of just throwing Unknown Command. This is a probable user behavior that seems not be handled completely.