Open vantemoon opened 1 year ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Removing a module that a contact doesn't currently take does not throw an exception
Ensure that the contact is not currently taking
gea1000
module 1 curr/CS2101 prev/CS2030S plan/CS2102 rm/GEA1000
No exception is thrown
[original: nus-cs2103-AY2223S1/pe-interim#1922] [original labels: severity.Medium type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
It is written in the developer guide that this is a design consideration. Regardless of whether the module existed or not, it would have been removed at the end of the execution. Even if it is considered a bug, it should not be medium but low severity.
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: [replace this with your explanation]
Team chose [response.Rejected
]
Reason for disagreement: I don't think the justification provided in DG is reasonable as even iterating though a list of 100 modules won't make the program significantly slower.
No error message is shown when the user executes "module user rm/ST2334" and ST2334 is not in the user's module lists.