nus-pe-bot
commented
4 years ago Team's Response
Hi there, thank you for taking time to test my feature. The error message shown is correct, the input after rounding to 2d.p. should be between 0 and 33 exclusive. I agree that the UG does not specify the lower bound while the error message does. This is a documentation bug in the UG, or at most a feature flaw.
I believe you have overestimated the severity of the bug. The bug severity was classified as high. Please review the Bug Severity Labels here. This bug is not one that "makes the product almost unusable for most users" because blood sugar concentration for most users would not be 0. This edge case bug "Appears only in very rare situations and causes a minor inconvenience only", strongly suggesting severity.Low.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low].
Originally [severity.High].
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue type
Team chose [type.DocumentationBug].
Originally [type.FunctionalityBug].
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
UG states (add command): BLOODSUGAR must receive exactly 1 valid parameter for concentration: con/VALUE Concentration (mmol/L) will be rounded to 2 decimal places. This rounded value must be less than 33 to be recorded successfully.
App: Entered "add rt/BLOODSUGAR dt/2019-04-20 13:32 con/0.0000". Expected: record to be added successfully since 0.00 < 33 Result: Concentration should only contain a positive real number between 0 and 33.0 exclusive after rounding to 2 d.p.