soc-pe-bot
commented
10 months ago Team's Response
That is not a functionality bug since the UG or DG did not state the alternative error message.
Tester should learn about the definition of a Functionality Bug from the course website:
The application returned the correct error message as stated in our UG/DG, and returning an alternative error message is a missing feature that is not supported by our application.
The input command is an "unknown command" because the command doesn't exist in our application, and therefore we have returned an appropriate error message that tells the user that the error they have made is using an unknown command.
If the tester is trying to suggest that we should provide a more detailed error message, then this should be a Feature Flaw instead.
The suggestion is a valid suggestion to improve usability, hence we will accept it as not in scope since the suggestion is a "Good to have".
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
From this error message it is unclear what error I have made and there is no suggestion to go to the help feature. A lot of users will be left confused at this point.