search

darrenangwx / pe

0 stars 0 forks source link

Blank spaces in front of module names not handled if edit through the storage file #5

Open darrenangwx opened 1 year ago

darrenangwx commented 1 year ago

image.png

image.png

As an advance user, I would like to edit the text file in the storage space. As seen in the first image, i added blank spaces in front of the module name to see if it was handled by the application. The first image shows that the module with blank spaces in front was successfully accepted by the application and the list /all shows the module name with blank spaces in front.

Justification: Since this is just a slight inconvenience for me as an advance user, this bug is listed with low severity.

nus-se-bot commented 1 year ago

Team's Response

We accept this bug as we do not handle the extra white spaces. However, this is mostly a cosmetic issue that does not affect the functionality of the program and hence we are lowering the severity to very low

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: The developers stated that this is mostly a cosmetic issue that does not affect the functionality of the program.

I disagree with this reasoning that it is a cosmetic issue and would like to maintain my Low severity rating due to the reasons stated below:

  1. Inconsistency in handling blank spaces: When the addition of blank spaces was done in the application, the blank spaces were handled gracefully. However, it fails to handle them correctly when the same edit was done on the module storage file. This inconsistency indicates a potential oversight that warrants attention, as it affects my experience when using the application.

  2. Negligent in storage feature importance: By lowering the severity to Very Low, it creates an impression that the developers are not prioritizing the storage feature and the user's perspective when editing storage files. The storage feature is a crucial component of the application and should be treated with due importance. Furthermore, in their User Guide, they did not provide any steps for the user on how to edit their storage file. They just gave a warning telling the users not to edit the storage file. This further strengthens my argument that the developers is treating the storage feature as non-importance, or is trying to hide underlying issues when it comes to editing the storage files.

Hence, I disagree with the developers changing this bug rating to VeryLow as this issue is not just purely cosmetic, and I would like to keep my original severity of Low.