Lack of instructions for manual testing for different cases for different commands

[Mnsd05]

The examples provided in the User Guide are not enough for other developers to fully understand what should be the expected outputs for different cases for one command. The authors may create a table including different cases and the expected output for each case, for example, what should be the expected output when the user gives a very big value for edit-stat command

[nus-pe-bot]

Team's Response

The examples provided in the User Guide serve as a way to explain the command in the most brief way possible. This is made to reduce clutter. (e.g. If every command example links to 2 other commands, our example would be very dense and confusing). For certain commands, we even have multiple examples to try to help the user see the different cases.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---