nus-pe-bot
commented
3 years ago Team's Response
As you may notice, 0001 is a year and it's in the format yyyy. It exists. Hence, it's appropriate to add this event to the list. In particular, there is no special constraint to the date like you can't have events happen before a certain point of time.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: if the app is build on the premise for the user of that year period and user can use it to plan for current and future event, it should be locked to a certain period start year and end year. It is irresponsible to allow all the years that are not properly mentioned(e.g. B.C. or A.D.). It should follow a certain year system to allow user to not accidentally enter a invaild year such as 0001
No details provided.
Description: No error handling on the year section of the assignment command
Actual: I've added this Event: [A][Not Done]Project (by: 0001/12/01 16:00) (Out of NUS): zoom Now you have 11 Events in the list.
Expected:
You entered the time in a format that is not accepted by this program. The format should be "yyyy-MM-dd HH:mm", and both date and time should be valid. For example, 2000-01-01 00:00