search

yyangdaa / pe

0 stars 0 forks source link

inproper exception handling in update event #6

Open yyangdaa opened 4 months ago

yyangdaa commented 4 months ago

image.png When updating an event, if the time format is entered incorrectly, the error message shows that the time format is incorrect but it goes back to main menu directly. The user can't retype the date / time, but instead the user has to restart from the first command again.   image.png

Moreover, the date time format is not specified in the user guide whether 2400 is allowed. Because 0000 is allowed but 2400 is not allowed.

nus-se-bot commented 4 months ago

Team's Response

It is common knowledge that the time format is from 0000-2359. Hence it is expected for the program to reject 2400.

Below link shows evidence that 2400 is only used in military context, which is not our target audience specified.

https://www.google.com/search?client=firefox-b-d&q=is+0000+or+2400+more+commonly+used#ip=1

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The issue with the event update process, where an incorrectly entered time format generates an error message but then prematurely returns the user to the main menu, has not been responded. This behavior disrupts the workflow, as users are unable to correct the date or time immediately. Instead, they are forced to reinitiate the entire process from the beginning.