nus-pe-bot
commented
5 months ago Team's Response
The parser is trying to read the weight as "85 65", which is not allowed. So the error message is correct from our point of view. The tester also mentions "not part of the valid tags", but there is no tag prefix (t/).
(also this has already been stated as an invalid command in the UG)
Items for the Tester to Verify
:question: Issue response
Team chose [response.IssueUnclear]
- [x] I disagree
Reason for disagreement: The issue here is that the problem is the lack of seperator (althought I used the term tag) between the 2 values in the range, not that of the application parsing it wrongly. Hence, the error message given is not specific enough. Additionally, I believe that error messages should not be seen "in the view" of a developer, but rather we should consider the perspective of users.
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
The issue here is not with a invalid weight command but rather having one more variable that is not part of the valid tags. The error displayed is not the actual error in question.