Open nkotaa opened 2 months ago
With the steps given by the tester, our app will take "ORIGINAL_DOES_NOT_EXIST" as the course code and "NEW_DOES_NOT_EXIST" as the course name. When viewing the timetable, it shows both course code and course name. They are two separate entities. Tester has misunderstood the command.
Team chose [response.Rejected
]
Reason for disagreement: Say I run add course ORIGINAL_DOES_NOT_EXIST y/1 t/1
. This is what the application responds with:
The UG neither explains this behaviour of add
nor defines what course name
means (in the glossary or otherwise). Thus it is reasonable for me to take course name
to mean course code + description in full. In other words, the application is asking me to restate the course to add.
If I then type NEW_DOES_NOT_EXIST
(either by accident or because I changed my mind on the course to add), I would expect either
NEW_DOES_NOT_EXIST
to be added (because the application allows users to change input mid-command); otherwiseInstead the application outputs
making me believe my input was ignored or something has gone wrong.
I believe this is a strong case of FunctionalityBug
with behaviour differing from normal expectations.
Steps to reproduce
add course ORIGINAL_DOES_NOT_EXIST y/1 t/1
NEW_DOES_NOT_EXIST
Expected
Either
NEW_DOES_NOT_EXIST
to be added to schedule or warning that initial and specified course names differ.Actual
Extra information
It seems the course name saved is a concatenation of both inputs. This is confirmed with the
view y/1 t/1
command which produces