nus-pe-bot
commented
3 years ago Team's Response
Thank you for pointing this out. Having said that, in normal usage, this is a very unlikely scenario as normal users would not be able to reproduce such a scenario. In addition, we clearly stated that only advanced user could modify the JSON file which makes such a scenario happens even much less frequently. In actual usage the app, modulebook3.5 will mark tasks with the same name and module code as duplicate and will throw an error to the user through GUI. Hence, we feel that the severity of this bug is very low as it will not affect the functionality of the application. Thank you again for your suggestion!
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: According to the PE guide, a severity of VeryLow means that it does not affect usage.
However, this bug will clearly affect usage. As a user, when I added 2 more tasks into the system, the counts and the charts do not tally (There are only two tasks on the right, but the counts on the left and the chart shows that there are 3 tasks).
This gives the user an incorrect depiction of the current state of ModuleBook. As the PE guide states, the flaw would cause occasional inconvenience to the users, as they would have to take note that there is a phantom task in the system which may affect their statistics.
Side note:
This is also inconsistent with the expected behavior (which is all data should be discarded).
When the JSON file was modified as below, the entire data file should have been invalidated (and the list of tasks is empty).
However, the number of modules is not updated accordingly as it still shows that there is one task in the system.