search

azfarulmatin / pe

0 stars 0 forks source link

Wrong Error Command for Edit function #2

Open azfarulmatin opened 11 months ago

azfarulmatin commented 11 months ago

Steps to Reproduce:

Launch the program and navigate to the edit command. Enter the command with the wrong order, putting category as last instead of the first parameter. Complete the edit operation.

Expected Result:

An error should appear, stating that the order of the command is incorrect.

Screenshot:

image.png

Actual Result:

The wrong error message occured, stating that the date entered is invalid. However, the date entered was correct and the main issue here is the wrong order.

Screenshot:

image.png

Comments:

The error message for the edit command should include validation against wrong order so that the users will not get confused with his/her own error.

soc-se-bot commented 11 months ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Not sure what error message saying about date format

image.png

The format says follow dd/MM/yyyydon?

[original: nus-cs2113-AY2324S1/pe-interim#1078] [original labels: severity.Low type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

This is a typo that will not affect usage of the app as the date format is clearly stated in the UG.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: The duplicated issue was related to a typo in the date format 'dd/MM/yyyydon.' However, the issue I identified was not about pointing out this typo. Instead, I intentionally tested a scenario where I entered the correct date format but placed the category as the last parameter instead of the first. Surprisingly, the error message instructed me to enter the correct date format, even though it was correct from the beginning.

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** The reported issue involves a specific functionality bug, as demonstrated by intentionally placing the category parameter last, which resulted in an incorrect error command. This action was meant to test and highlight a functional discrepancy, not a documentation error. I believe maintaining the classification as a functionality bug is more accurate and reflective of the observed behavior.
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]