Open lightz96 opened 4 years ago
Hi, we accept that the UG should have mentioned that v1.4
does not support case-insensitive entries for module codes.
We have lowered the severity to medium as it only causes a occasional inconvenience to users but the product is still able to operate normally.
However, we were unable to reproduce the situation where no error message is shown, as it does show an error message in our own tests:
Team chose [response.CannotReproduce
]
Reason for disagreement: I realized that the bug only occurs when you execute the same invalid command again (does not need to be directly after).
However, did the team try to run the same commands multiple times? (As stated in the instruction: response.CannotReproduce: You are unable to reproduce the behavior reported in the bug after multiple tries.) It should produce the same behavior as stated in the issue.
E.g.
showmod m/2103
showmod m/2103
It should result in NullPointerException as shown below:
The expected behavior should produce an error message regarding of how many times the same invalid command was executed.
Team chose [severity.Medium
].
Originally [severity.High
].
Reason for disagreement: [replace this with your reason]
Team chose [type.DocumentationBug
].
Originally [type.FeatureFlaw
].
Reason for disagreement: The bug type should be FeatureFlaw
since it is regarding the inability to produce an error message after executing showmod
.
No error message shows when I entered
showmod m/2103
.