Open wj331 opened 1 year ago
User: As shown in the screenshot you shown, it is explicitly stated that edit command works for 6 different fields, so we are not sure why having only 2 examples would make the user think that the edit command only works for 2 fields. After all, examples are only sample inputs for the user to see how an input would look like.
Tester: As a tester, you would be expected to see the DG, and there is an entire section in the DG about manual testing where you can simply copy and paste values, not sure why you insist on solely using the UG as a reference for testing.
Team chose [response.Rejected
]
Reason for disagreement: Well, if you have to ask me to refer to the DG when I am at the UG, it is obviously a UG bug that I am picking up on. So this means the team partially admits that the UG inputs are incomplete and is asking me to refer to a more complete version in the APPENDIX of the DG
Furthermore, it is seen in the course website that having Not Enough examples is one form of UG bug as seen in the screenshot below:
As seen, only 1 example that edits 2 fields
phone
andemail
is given, when in factedit
command:edit INDEX [r/ROOM] [d/BOOKING_PERIOD] [n/NAME] [p/PHONE] [e/EMAIL] [rk/REMARK]
works for up to 6 different fields.
I had to manually type in the d/BOOKING_PERIOD which is: "2023-01-01 08:00 to 2023-01-02 11:00" long with strict formatting requirements
Caused great inconvenience and testing issues as a user and tester