Open PDHung1104 opened 2 months ago
The bug is caused by the use of :
in the username Giang : 1000
. There is a :
in the username string that is used as a delimiter for our database. Therefore, upon exit and reentry of program, the expense dkjsad
was loaded in incorrectly which caused the wrong value to be shown for the expense upon entering the list
command.
This error is not high as it is only produced when fields entered contain :
in them. Most users are unlikely to enter these characters on a general basis. As such, we think that the severity should be medium because this is a flaw that causes occasional inconvenience to some users that use the :
in the description
, payee_name
and payer_name
. Furthermore, they can continue to use the product because their data is still saved, and they can still use other features. Hence, this will not make the product unusable for most users.
This is a duplicate of issue #87 as the user entered the :
character in one of the parameters which caused the bug.
[The team marked this bug as a duplicate of the following bug]
application crashes upon use of balance command for decription with #s in expenses
make sure alice and bob are members of the group expense list used
command to add expense: expense stuff#8 /amount 9.00 /paid alice /user bob
upon exiting and entering the application, enter the group with the added expense and type
balance alice
[original: nus-cs2113-AY2324S2/pe-interim#75] [original labels: type.FunctionalityBug severity.High]
[This is the team's response to the above 'original' bug]
The bug is caused by the expense command:
expense stuff#8 /amount 9.00 /paid alice /user bob
. There is a#
in the expense description that is used as a delimiter for our database. Therefore, upon exit and reentry of program, themoneyList
parameter in theGroup
class was not initialised which caused an illegal access error when entering thebalance alice
command again.This error is not high as it is only produced when fields entered contain
#
in them. Most users are unlikely to enter these characters on a general basis. As such, we think that the severity should be medium because this is a flaw that causes occasional inconvenience to some users that use the#
in thedescription
,payee_name
andpayer_name
. Furthermore, they can continue to use the product because their data is still saved, and they can still use other features. Hence, this will not make the product unusable for most users.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]
I added a new member called
Giang:1000
and the program accepted my input.Then, I added a new expense and added
Giang:1000
as an user. After that, I exited the program and ran it again. The program displayed the wrong split amount.