search

kervyntan / pe

0 stars 0 forks source link

Developer Guide (Instructions for Manual Testing) - Point 3 doesn't hold during usage of the application #16

Open kervyntan opened 7 months ago

kervyntan commented 7 months ago

Screenshot 2024-04-19 at 5.35.48 PM.png

Description

Using the application, I was able to add schedule a meeting where the start time was before my system current date (19-04-2024):

Command ran: schedule 4 s/23-04-2024T16:00 e/23-06-2024T17:00 mr/online meetings.

Expected Behaviour

Error message thrown since start date is before my system current date, according to the documentation.

Actual Behaviour

Application allows the command to be successfully executed.

nus-se-bot commented 6 months ago

Team's Response

Thank you for the bug report.

Our team has decided to reject this bug as the given command: schedule 4 s/23-04-2024T16:00 e/23-06-2024T17:00 mr/online meetings. is a valid command given that the current system current date is 19-04-2024. As 23-04-2024 is after 19-04-2024, the expected result should hold as stated in the DG.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: The User Guide (above screenshot in original bug) explicitly states that the provided meeting start date MUST BE the same as the system's current date, not before or after. From a user's perspective, they are unlikely to delve into the DG for details on how to use these commands and will instead rely on the information laid out in the User Guide for their troubleshooting measures. This could result in conflicting behaviours and frustration on the user's end on how to use such an important command in the application.