search

MonkeScripts / pe

0 stars 0 forks source link

leap year dates #11

Open MonkeScripts opened 2 months ago

MonkeScripts commented 2 months ago

image.png

nus-pe-bot commented 2 months ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Thank you for testing out leap years.

However, in the image you have attached, the date you have keyed in, 29-02-2026, is not a leap day. I am confused by this, given that the title of your bug report seems to be leap year dates, which is why I assumed that you would test dates of leap days.

Additionally, our application does accept leap days, as can be seen below.

image.png

I hope you understand my decision to tag this as IssueUnclear.

PS. If you are wondering why the date is changed to 28-02-2026 in your scenario, my groupmate has described it as follows:

This is an interesting catch. I was able to reproduce this bug using different dates, such as 31-02-2025 (which is resolved to 28-02-2025), or >31-06-2024 (which is resolved to 30-06-2024).

I have done a bit of research on this, and this appears to be an odd quirk of the java.time.format.DateTimeFormatter class.

This was an oversight on my part, as I wasn't aware of the different types of year formatters that can be used.

Items for the Tester to Verify

:question: Issue response

Team chose [response.IssueUnclear]

Reason for disagreement: [replace this with your reason]

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]