nus-se-script
commented
3 years ago Team's Response
Pressing left and right arrow keys are possible, but you have to click on the tab using the mouse first and that is not a use case that is important (the user has to click back to the command box to type in his command anyway). Our target users are CLI users who do not like using the mouse, thus we feel that this control method is very niche and need not be mentioned in the UG. Only important details that are relevant to the use cases should be documented.
Even if this is accepted, it should not fall into the Low category as for it to be considered Low, it should cause an inconvenience, but this does not.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: The control method of using the mouse to click on tabs is documented in the UG which goes against the team's claims that niche control methods are intentionally not mentioned in the UG. This suggests that either the team was not aware of this unintentional feature, or that they were aware of it and missed out on its documentation.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: Since the control method of using the mouse to click on tabs is documented in the UG, users can be expected to perform this operation. In that case, users should also be aware that an accidental press of the arrow keys after clicking on a tab will switch tabs. Hence, not making this behavior known to users can cause inconveniences in case of mistypes.
In addition, this is not a cosmetic flaw; it directly affects usage. This should not have a severity of VeryLow.
If user clicks on either Students, Classes, or Timetable tab, they are able to navigate between them using the left/right or up/down arrow keys. This is an additional functionality that is not documented in the UG.