nus-se-bot
commented
1 year ago Team's Response
As the UI says, it has to be a "valid positive number"
The testers input is invalid and beyond the probable usage of the app, and the app did not crash and successfully prevented such an input from being considered as valid
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thank you for the response.
With regards to your second point on the input being beyond probable usage of the application, that is correct. However, the bug is targeting the UI component of the error message.
In particular, as you have mentioned, it has to be a "valid positive number". In the screenshot provided above, the number provided is a valid positive number, and is also within 2 decimal places. However, the error message informs the user to believe otherwise as it says: Input must be a valid positive number, with at most 2 decimal places. Both conditions are fulfilled here.
In addition, despite the truth in the number being probably usage of the application, it is an input that still should be considered because there is no amount limit imposed in the User Guide. Thus, it should be handled accordingly with the proper error message
The application produces a misleading error message when a very large amount is entered
The amount provided is indeed positive, and is within 2 decimal places. This bug occurred due to the double overflow, thus resulting in a negative number -- being rejected while the amount provided is indeed valid.