freddychenyouren2 / pe

0 stars 0 forks source link

Ambiguous output message for `findfreetime` when no one is free #3

Open freddychenyouren2 opened 7 months ago

freddychenyouren2 commented 7 months ago

image.png

In this scenario, group1 consists of Alex Yeoh and David Li

The following command is done: findfreetime g/group1 d/150

Expected: An error message to indicate that no one in the team is available

Actual: "These are the available timeslots" but with no timeslots.

The user could accidentally entered an extra "0" at the back, or could have gotten the duration of the meeting wrong to produce such an error, which may not be trivial. A further improvement could be to maintain command with the erroneous input in the command box, rather than wiping it out after the user hits enter and potentially causing confusions. (After all, the target user types fast and might not catch typos)

soc-pe-bot commented 7 months ago

Team's Response

There is documentation on the UG and DG on what the outputs are. Users should know what having that output means from a quick glance of the UG. For example, since there are no time slots displayed, it means that there is no available time slot for the group to meet with the indicated duration.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [Thank you for your response.

While it is acceptable that the target users (University Students) would infer that having no timeslots displayed means no one is free, the issue here is more on what if users had a typo in the timing. The user could have wanted to enter findfreetime g/group1 d/20 instead of findfreetime g/group1 d/200 (Extra 0). The user may believe that the former was entered but actually the latter was entered instead. Without a clearer output message, such as showing what is the duration user entered, the User Experience may be negatively affected. This is because users would either have to figure out whether he/she has entered the duration wrongly, or accept that no one is free when actually some people are free.

I hope this clarifies on what was the focus of the bug report! Thank you for your kind consideration and understanding.]