[DG] Uninformative Expected output in Manual Testing

[LowTL]

The Manual testing explains the expected output briefly, but does not show what the actual expected output is. There could be confusion in users performing manual testing when they perform the tests, as they are unsure of what these expected outputs should look like.

[nus-pe-script]

Team's Response

The developer guide is for developers not for users, the users would refer to the user guide when they use our app. The developers just need to know what is the expected outcome when the commands are entered.

According to the course info, we only need to provide some test inputs for testers to copy and paste which we have done, further information can then be found in the user guide in order to minimize repetition of information.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---