nus-pe-bot
commented
4 months ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Error message for invalid date input does not match error.
) As shown above, when I input an invalid date that follows the date format specified , I don't get a specific error saying that my input is an invalid date
[original: nus-cs2103-AY2324S2/pe-interim#4231] [original labels: type.FunctionalityBug severity.Low]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
MM in dd/MM/yyyy is a common abbreviation for the month, and since the input is not between 1 to 12, it is not following the format as the error message stated. Hence, the error message is valid and specific enough.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue response Team chose [`response.Rejected`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
steps to reproduce: list-until-date o/32/10/2028
expected: error message telling me invalid date
actual: Appointment should only contain numeric values in dd/MM/yyyy or yyyy-MM-dd format, and it should not be left blank
even though the format follows the ug format, the error message does not give the user information on what went wrong