Manual Testing section lacking

[malcolmang]

The Manual Testing section does not provide any additional information to aid in explaining how to go about testing the program. It only has references to other sections (like Getting Started or the User Guide), but doesn't provide any information of its own.

Example:

[nus-pe-script]

Team's Response

Hi there,

As you have mentioned, the additional informational such as the command syntax can be found in the user guide and Getting Started does get the program running and exit the program. It would not be feasible for us to copy the information into the developer guide, when the user guide already exists.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Manual testing encompasses more than a list of commands for the program. For example, in AB3 https://se-education.org/addressbook-level3/DeveloperGuide.html#appendix-instructions-for-manual-testing

The manual testing section contains information for testing various commands with different parameters, as well as their expected outcomes. It even has instructions for simulating corrupted/missing files, etc. This is not present.

The bug report was not expecting you to list the same info as the User Guide: it is simply that the Manual Testing section should not only contain information from the User Guide.

---