search

mrweikiat / pe

0 stars 0 forks source link

DG : Manual testing, edit command test cases not extensive enough #11

Open mrweikiat opened 3 years ago

mrweikiat commented 3 years ago

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.

image.png

A good example will be the delete feature, that address all possible test cases with boundary conditions

image.png

nus-pe-bot commented 3 years ago

Team's Response

No response provided.

The 'Original' Bug

[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

image.png

Expected documentation similar to delete command:

image.png

[original: nus-cs2103-AY2021S2/pe-interim#763] [original labels: severity.Low type.DocumentationBug]

Their Response to the 'Original' Bug

[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.

photo_2021-04-19 19.22.44.jpeg

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.

Screenshot 2021-04-19 at 19.24.44.png

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 reason]

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

Reason for disagreement: [replace this with your reason]