Error message is not specific enough when there are empty parameters

[chydarren]

Though it is valid that the application is unable to understand the command, the message may be too generic for the user to understand what went wrong with his input. Instead, the team has to specify that the parameters cannot be left empty, etc.

[soc-pe-bot]

Team's Response

Valid point, but not in the scope of our v2.1. And be an optimize feature in future versions

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: As the team has considered to catch the command with empty parameters, and is caught as shown above, the correct message should be displayed to inform the user of the error that has been caught, instead of providing a generic message The system is unable to read your command, please try again. for many types of errors that they have caught.

Hence, as per the below module guideline, I believe that the above is a feature that they have included in v2.1 (i.e. to catch the empty parameters), and hence they need to provide a more accurate error message for the user.

---