Open parth-io opened 1 year ago
This was mentioned in the PE brief. Testing problems caused by integer overflow and intentional sabotage is not in the scope of the PE.
[The team marked this bug as a duplicate of the following bug]
Show command shows different/wrong error message for same kind of error
Show command shows different/wrong error message for same kind of error
When I choose a relatively small out-of-bounds index (e.g. 100) for the
show
command, the application shows invalid index error, which is correct, because the index is out of bounds.However, when I choose a larger out-of-bounds index (e.g. 10000000000000000000) for the
show
command, the application is shown invalid command format.Example
show 100
show 10000000000000000000
This causes the error message to become generic, hence I put it under functionalitybug.
[original: nus-cs2103-AY2223S1/pe-interim#1715] [original labels: type.FunctionalityBug severity.Low]
[This is the team's response to the above 'original' bug]
This was mentioned in the PE brief. Testing problems caused by integer overflow and intentional sabotage is not in the scope of the PE.
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: [replace this with your explanation]
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
Pre-req: 1 message exists
To reproduce: Type
m d 11111111111111111111111
Expected: The error message should read "The message index provided is invalid."