soc-se-bot
commented
5 months ago Team's Response
This is fair, we accept that this is a limitation of our input parsing process for integer values as the error message is inaccurate.
However, the issue is caused by the large input value of "9999999999999.....", which the target users of our application would never enter normally and what our team would consider as extreme user behavior, as defined in the image below.
Reasonable values entered by the user would not trigger this error message and would work fine, hence, the issue would not occur under expected usage. Our target users are small businesses, so its highly improbable that they would have item stock/quantity that exceeds even a million. Additionally, it is important to note that such inputs does not cause our application to crash, despite it displaying an incorrect error message.
Therefore, the team considers this a valid error message issue but out of scope due it being caused by extreme behavior.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
In all three inputs, the input is a whole number, but the error message is indicating that whole number is not being inputted.