nus-pe-script
commented
2 months ago Team's Response
Format does not only refer to the type of input (numbers, letters) it can also refer to the formatting itself (1 digit, 100 digits). As such, the error message still accurately describes the error in the input.
Furthermore, such an input can be considered to be a problem caused by extreme user behaviour. As such, we are rejecting this issue.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree that the "error message still accurately describes the error in the input" as it does not mention that the issue is because the number is of 100 digits and not of the required digit. Furthermore, there is nothing mentioned about the limit in digits within the UG.
Furthermore, the problem is not that the users input is not being handled properly which is what the section "Problems caused by extreme user behaviors" is talking about, as mentioned in the bug report, the issue is that the error message thrown is different for the same type of error which does not make sense and is a lack of consistency.
Hence, I still strongly believe that this is a bug.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** The team has not given a reason for why the severity is Low and not Medium
When i first enter a considerably large number, it throws an error stating that the format of the number is wrong. However, the number is an integer and so it is indeed not wrong.
But when I enter a number that is large, but not too large, it throws an error stating that the classes attended must be less than 500.
Shouldn't the same error be shown for both the cases?