nus-pe-bot
commented
4 years ago Team's Response
Problem: Although under user guide 3.4.Quiz note on UI, “You can adjust the size of the split pane by sliding the window separator between the two windows to fully see the whole question”
Response:
- This is what I stated in my userGuide:
Note on UI: Modulo quiz uses dark theme to prevent users to strain their eyes by staring at their computer window too long. You can adjust the size of the split pane by sliding the window separator between the two windows to fully see the whole question. Go to 3.4.6 to see the details.
- If you noticed I try to redirect you to the 3.4.6 from the website or the 6th instruction from my userGuide. If you go to this portion of the userGuide you will find this:
''' Details of a selected question:
Show the details of a selected question. This details will show the whole questions that is truncated from the preview window and reveal the comment/explanation from the selected question. '''
Format: detail [INDEX]
Usage: [INDEX] is the index/row from the question that you want to see.
Example: detail 1
- So it will display the question into the right screen and also fully show the questions
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Your explanation does not resolve my issue. I'm referring to the priority (circled in the screenshot below for further clarification):
Note that no matter how much I resize, if the question is long, it's going to be converted into ellipses.
In no area of your explanation does it talk about the priority, neither does the UG say that I will have to use the details to see the priority of a question; it only talks about how the question is truncated (the priority of a question is not part of a question, after all), and does not talk about how the priority is replaced by ellipses.
In the event you do not understand what I mean by priority, I'm using the definition provided by your UG:
It is a small issue, thus I have put it as small severity. But this is something that should be addressed rather than written off as something that is covered in the UG when it isn't.
Also, I note that this response is very similar (if not the same?) with issue https://github.com/crazoter/pe/issues/18. Is there a bug with CATcher or is this done on purpose by the developer?
:question: Issue type
Team chose [type.FeatureFlaw].
Originally [type.FunctionalityBug].
- [X] I disagree
Reason for disagreement: I'm assuming that the developer intended (..?) for the priority to be replaced with ellipses. It's more of a documentation bug if that is the case.
Expected Behavior
The priority is on a new line, for example.
Current Behavior
Environment
Windows 10 64 bit java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)