nus-pe-bot
commented
3 years ago Team's Response
The manual testing section is to guide another developer on how to test the different commands and their variations. Our email, edit, select and tag commands support bulk actions with special indexes (shown and selected) or multiple indexes.
These four commands handle each bulk actions independently and a separate logic code is used to handle each variation. Thus if edit selected is working, it does not mean email selected is working. Similarly, if edit selected is working, it does not mean edit shown is working. On top of that, the four commands when executed with different indexes will also produce different results.
Therefore, writing manual testing instructions for each of these commands and the different test cases for all the indexes is reasonable and should not be seen as repetitive.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree.
The descriptions for delete persons and email persons are clearly repetitive.
In the delete persons' description, point No.5 delete 0 is something email persons' description doesn't have, but email 0 can also be added as point No. 5 into email person's description. Therefore, their descriptoins are repetitive.
When writing delete persons command, they can just add a note at the back stating "Note: This set of test cases can be similarly performed for email persons command by replacing delete with email. "
DG: instruction for manual testing part repetivie