Open mkeoliya opened 3 years ago
We are just using an existing, popular Java library LocalDate.parse() method. This LocalDate library is also recommended to all students to use in iP by Prof Damith. This way of error handling is decided by the Java libary developers and not up to us to decide. Therefore, this is not in the scope.
Team chose [response.NotInScope
]
Reason for disagreement: The lack of date validation does not satisfy either of the two conditions for an issue to be out of scope, since the UG doesn't acknowledge it nor does the system provide a suitable error message.
Further, the user (or tester) shouldn't be concerned with the implementation of a functionality or which class is being used, and the behaviour should either be as expected, or should be specified clearly in the UG. Regardless, do note that it is almost trivial to sanity check a date using the LocalDate
Java libraries : here.
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: Rejecting an issue does not mandate decreasing its severity. The lack of an error message while accepting an invalid date is not purely cosmetic or a typo, and does not justify the VeryLow
tag.
Steps to Reproduce
Expected: Error showing invalid date, because 29th Feb in 2019, and 31st April in any year don't actually exist. Actual: The booking is added anyway.