nus-se-bot
commented
3 years ago Team's Response
The section seems like an optional field and many teams did not include it in their DG. Furthermore, manual testing can still be done reading the UG.
It is also stated in the website that we should not duplicate details in the UG. Hence the testing details in the DG only involves suggestion for testing features that are not mentioned in-depth in the UG (eg. archiving and how to get the different appointments status)
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I disagree to the view "Hence the testing details in the DG only involves suggestion for testing features that are not mentioned in-depth in the UG (eg. archiving and how to get the different appointments status)". In the DG for AB3, there is also a manual testing case of installing and downloading the jar file.
I feel that the manual testing section is suppose to state simple use cases so that future developers can test and then conduct exploratory testing themselves. "Clear" command to me has a very important and influential function for your app and I strongly suggest to mention it under the "Manual Test" section so that developerse would not miss out thoroughly testing this crucial feature.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
I feel that more cases such as change, clear, find commands can be added to Manual testing section so that future developers would not be shocked by the commands expecially 'clear' command that clears everything.