search

denzelcjy / pe

0 stars 0 forks source link

Misleading error message for setting budget #2

Open denzelcjy opened 1 year ago

denzelcjy commented 1 year ago

Steps to reproduce: key in budget set /a /c /c

Expected: an error message saying that there should not be a slash in the parameter

Actual: an error message saying that i have input a string of >30 characters

Screenshots:

image.png

soc-pe-bot commented 1 year ago

Team's Response

we would not count it as a bug since the app is working as intended and not accepting your input as a valid input

The 'Original' Bug

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

Misleading error message with very large budget amounts

The application produces a misleading error message when a very large amount is entered

image.png

The amount provided is indeed positive, and is within 2 decimal places. This bug occurred due to the double overflow, thus resulting in a negative number -- being rejected while the amount provided is indeed valid.

[original: nus-cs2113-AY2223S2/pe-interim#1350] [original labels: type.FunctionalityBug severity.Medium]

Their Response to the 'Original' Bug

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

As the UI says, it has to be a "valid positive number"

The testers input is invalid and beyond the probable usage of the app, and the app did not crash and successfully prevented such an input from being considered as valid

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: Hi, I do not think this is a duplicate since it is handling of different error messages. Mine is regarding the error message that the string is clearly below 30 characters but I am getting an invalid error message.

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** If the dev team thinks that this UI specific problem does not affect the usage of the app as intended, the response should be out of scope instead of rejected.
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]