Error message inconcsistent with similar input

[jingyaaa]

Putting myself in the shoes of a user who does not know computing, I would be genuinely confused at the difference between the two error messages given that I my inputs are both numbers

[nus-pe-script]

Team's Response

Differing behaviours are caused by extreme user behaviour.

Invalid task number is returned as the number given as input causes an integer overflow. Values between (inclusive of) 1 and 2,147,483,647 (max value of type int) will return Task number does not exist. Values beyond 2,147,483,647 will result in Invalid task number.

Cause is similar to Issue #2620.

The 'Original' Bug

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

Input big number for add-stat value

When I give a very big number, both negative and positive, the program tells me to give an integer although the value is already an integer

---

_{[original: nus-cs2113-AY2223S2/pe-interim#2449] [original labels: type.FunctionalityBug severity.Low]}

Their Response to the 'Original' Bug

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

Buggy program behaviour is caused by extreme user behaviour.

Bug is caused by integer overflow. Values between -2,147,483,648 and 2,147,483,647 (min and max values of type int) will result in expected behaviour.

Valid negative values and zero throws the following error:

ERROR: Integer provided should be above 0

Valid non-zero positive values will successfully update the stat.

Items for the Tester to Verify

❓ Issue duplicate status

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

• I disagree

Reason for disagreement: The problems mentioned in the 2 reports are different. While one talks about wrong error message due to the word "integer", the other talks about the presence of two error messages resulting from similar user inputs.

---

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: While the example that I have given above seems to show extreme user behaviour, it is undeniable that the same issue applies if the task number is 0. The error messages given for 0 and 100 are different and inconsistent, hence possibly confusing the user.

---