search

kervyntan / pe

0 stars 0 forks source link

Scheduling feature: Command succeeds even though START_DATETIME is before my system's current datetime #8

Open kervyntan opened 5 months ago

kervyntan commented 5 months ago

Screenshot 2024-04-19 at 4.51.52 PM.png

Description

(Just to confirm, in the User Guide it states that the START_DATETIME should be after system's current datetime - does system refer to the machine the user is running on? It's a little ambiguous) Added a meeting date that took place before today.

Steps to reproduce

  1. Launch the application for the first time to load initial data.

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

Expected behaviour

Error thrown that START_DATETIME was not after my system's current datetime of 19-04-2024T16:51:00

Actual behaviour

Meeting scheduled

nus-se-bot commented 5 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 the bug report.

However, our team has decided to deem the bug as invalid as the START_DATETIME given seems to be after the current system datetime that is stated. 23-04-2024T16:00 (input) is later than 19-04-2024T16:51:00 (reported system datetime).

In response to the question on system' current datetime, the system does indeed refer to the machine the user is running on.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]