ketweeen / pe

0 stars 0 forks source link

Unable to input 31 as date #5

Open ketweeen opened 11 months ago

ketweeen commented 11 months ago

image.png Some months have 31 days... But if it's because it is assumed to be November or whatever the current month is (and thus can only be up to 30), it then should be noted at the error message or developer guide or user guide.

nus-se-bot commented 11 months ago

Team's Response

We have noted in the UG if the month is omitted, it will assume the month the user want to input is the current month. Then it is correct to reject 31 as input for date. Screenshot 2023-11-18 at 16.07.52.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I fail to see where the UG explicitly states the app assumes the month as the current month. While your example might imply this fact, I still feel that this is an important assumption that needs to be stated explicitly both in the UG and error message.

As a new user using you app, when I read the error message Number 31 is out of range: 1 - 30, I thought the app simply couldn't accept 31 as a value for day, not because the current month only has 30 days. Since is only 30 days, I would have expected an error message something like Number 31 is out of range for the current month: 1 - 30.

I feel that this then would be an issue when user accidentally forgot the current month only has 30 days and then becomes confused to why it does not want to accept 31. However, I do agree that this is indeed a rare case, and therefore I would also agree for this bug to be marked as severity.VeryLow.