Open SpdPnd98 opened 2 years ago
You can view details 8
like static analysis and details test4
like dynamic analysis. The application knows that details 8
will never work and so it doesn't bother to try searching at all. This is consistent with delete 8
. However for details test4
, it behaves like find test4
and doesn't know until it searches it and finds no person matching. These command behaves very predictably and are consistent with their analogues (delete
and find
). I do not see any inconsistent behavior which requires it to be documented. The response by the application is intuitive as well and so the user won't be confused
Team chose [response.Rejected
]
Reason for disagreement: The developer's response was not documented in the UG. As a user, I would not know anything about static/dynamic analysis. There was no mention of the similarities between details
and other commands as well, therefore the bug should not be rejected.
Furthermore, the explanation given by the developers is not satisfactory, as it is an implementation detail, not related to the User Guide. As a user, I am expecting the same outcome if I am checking a detail of a person that does not exist on the list. Either fix the consistency of the behaviour, or add the developer's response to the UG/DG.
If a user enters
details test4
, a name that doesn't exist in the IG, it still directs users to a details page, which is empty. This behaviour is not defined in the UG.However, entering
details 8
shows that no user at index 8. The two behaviours should be the same.