Open ibrahimisramos opened 2 years ago
The tester here has deliberately given an invalid date in the month of February which usually only has 28 days except on leap years. As stated in our UG, this application is for clinic adminstrators who are most likely to work on days and dates that exist in this world. They can refer to the date often shown on their desktop or smartphone screen to correctly get the date that day. Hence, I believe that this bug is NotInScope because the target user can and should refer to the correct date of the day easily, even if they key in non-existent date in this application by mistake. Also, it would be more likely that they will key in an incorrect format rather than a non-existent date.
Team chose [response.Rejected
]
Reason for disagreement: Hence, I believe that this bug is NotInScope because the target user can and should refer to the correct date of the day easily, even if they key in non-existent date in this application by mistake.
A check would be good to have in future versions and as mentioned, could be marked as not in scope instead of being rejected!
When I put in an invalid date of registration, it is not helpful to be shown this message telling me that my date is in invalid format as it technically is. Perhaps an invalid date might have been a better error message? Or if there are plans to incorporate a GUI that will prevent invalid dates, it could have been stated clearly!