nus-pe-bot
commented
4 years ago Team's Response
This is a valid date... 4444 is a valid year, although it is very far away. As such we reject this.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree with the response from the team as this issue goes beyond it still being "a valid year".
A certain resonable range should be set to prevent making appointments beyond that. This is because:
- Being able to create an appointment equates to being able to book an appointment as per the application's feature. Users now can book an appointment with a doctor for 2000 years later which does not logically make sense (Expected age of humans).
- Hospital may not exist by that date.
- By being able to make an appointment beyond a reasonable range, it is expecting the users (administrators) to be able to predict that far into the future regarding doctor/equipment availability and capacity load for the day.
Thus this should be considered a valid issue and address to ensure the usability of the application for real life scenarios.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: 
Referring to the image above and the explanation in the above disagreement, this issue goes beyond what is a very low severity bug (Cosmetic and minor spelling errors). At minimum, this should be considered a low severity bug even if not medium as it causes inconvenience to the users but is still unlikely to affect normal operations. Will leave it to the evaluator to decide what is best.
Input: 4444-12-12 Expected: Error message Actual: New appointment created!