Open SharlynLui opened 5 months ago
Thanks for pointing this out. Through many attempts to reproduce the issue, we found out that the Storage
class incorrectly initiates all the classes associated to the user results, as well as the topic attempt status.
Duplicate as the root cause of the reported bug is the same.
[The team marked this bug as a duplicate of the following bug]
Index out of bound at the end of results
Text at the end of results shows "index out of bounds". Can consider reviewing code to not print outside of bound.
[original: nus-cs2113-AY2324S2/pe-interim#1241] [original labels: severity.Low type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
Thanks for pointing this out. Through many attempts to reproduce the issue, we found out that the
Storage
class incorrectly initiates all the classes associated to the user results.Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: This bug should not be a duplicate of the original bug because they are not of the same severity even though I agree that solving the bigger bug might also solve the original bug.
The original bug focused on the extra output from the app. This current bug focuses on the function of tracking the attempted topic and score promised by the app not delivered which might be due to the same reason why there was an extra output.
Given the explanation of why the bug is of medium severity below, it should not be considered a duplicate to avoid inheriting the same severity.
Under "list", topic 2 is unattempted. However, when viewing results, it shows that I have a result of 200% for topic 2.