nus-pe-bot
commented
3 years ago Team's Response
The goal of our app is to deliver our target audience a viable functional product, not to comprehensively defend every way the doctor can deliberately try to mess up our product. In what scenario would a such a weight/height (9999...) be valid? Our product provides ample space for multiple appointments and medical records to be added as we foresee that to be an issue, but nobody would realistically have such a long value in the height/weight field.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: It is true that this bug occurs when long numbers/strings are inputted, and perhaps it is not common that the user will key in such a long strings. However, it still remains that there is a problem in the command itself.
When we do checks, we go beyond the system requirement and system specification, to see if the system will fail gracefully when an "out-of-bounds" parameter is fed into the system. Regardless, the app is not dealing with an exceptional case here correctly, and this needs to be rectified even if users will not encounter this bug most of the time.
Additionally, if we assume that users will follow all the commands exactly as we intended (the purpose of the command, the format of the parameters), then there is no need to check for errors anymore.
When I type in a long input in any fields, the GUI gets cut off.