nus-se-script
commented
1 year ago Team's Response
Based on the tester's report, the screenshot already shows the restrictions for the INDEX input, which is that it refers to the index number shown in the displayed inventory list.
The team does not feel a need to additionally specify an upper limit because the "upper limit" would depend on the user's total number of inventory items. This is variable depending on the user's usage of the application and would be impractical to specify this in the user guide.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree. Based on what i found there a theoretical upper bound of 2,147,483,647 set by the team when putting in numbers that are too large.This can be misleading to users who believes that there is not a upper bound especially testers when they want to test what conditions the app can be broken.Maybe the severity can be lowered to very low but it is not fair for the consumer/user to be deceived that the app is infallible.Even if cannot hit that target i will feel decieved or duped as i believe it can go to infinity even based on what the team has said.When you buy something you may not use every aspect but when i test it better be what it says am i right?
Based on the following index does not specify a definitive upper limit. When tested just now there was an upper limit and it throws out the wrong error.Specifying the upper limit will help