Open mrweikiat opened 3 years ago
No response provided.
[The team marked this bug as a duplicate of the following bug]
DG : No test cases specified for boundary test cases, difference in error message
tried command : edone 1000 Expected: All indexes provided are either invalid or references events that are already completed Actual : All indexes provided are either invalid or references events that are already completed -- same
However, there was no test cases specified for after a certain integer, the error thrown will be different. For eg:
tried command: edone 100000000000 expected: All indexes provided are either invalid or references events that are already completed Actual: Invalid command format
Expected documentation similar to delete command:
[original: nus-cs2103-AY2021S2/pe-interim#763] [original labels: severity.Low type.DocumentationBug]
[This is the team's response to the above 'original' bug]
Manual testing is only a start, not meant to be comprehensive and also not meant to include all test cases.
Regarding the error message, 100000000000 exceeds 2,147,483,647 so it is not an index and therefore the error message is correct, since the command is missing an index.
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 reason]
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your reason]
Similar to the add command test, this application has quite a number of attributes. The DG manual testing only let user test editing of -a and -t However, there are still other attributes like name, phone number, address, email, birthday -> at least 5
The testing cases should be more extensive, component under DG bugs.
A good example will be the delete feature, that address all possible test cases with boundary conditions