vibes-863 / pe

0 stars 0 forks source link

Error message not specific #3

Open vibes-863 opened 2 months ago

vibes-863 commented 2 months ago

image.png

When I try to enter a decimal number for the classes, it does throw an error, however the error just says that the format is wrong and gives an example of 12. However, it is not easy to infer from this that the format error is that it should be an integer value. The example does not help make it clear either.

soc-pe-bot commented 2 months ago

Team's Response

In the context of the program, even a class with 1 student is still considered a class attended. Moreover, it is quite rudimentary to say that the classes attended has to be a whole number, as partial fractions does not make sense in this context. It is hard to agree that this is a feature flaw as in no extreme circumstances would a tuition centre admin need to input 0.1 for classes attended. There is a lack of logic here.

Lastly, the program has generated a purposeful output message, with an example to boot. This is conveyed in the UG and DG as well and the user should know that the programme only accepts whole numbers.

If the user tries to put a float or a double, the user would be prompted with the above error message, and hopefully, they would be able to put 2 and 2 together and make 4. We believe the average population intelligence allows the inference that decimal places will not be accepted.

In fact, not accepting decimal places is a safety feature to prevent accidental input of decimal places and hence eliminate typos.

Hence, this feature is as intended and works against what the proposed bug suggests.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: The bug report never mentioned that the feature did not make sense, it mentioned that the error thrown by the app is not clear enough. It is to do with the specificity of the error message.

image.png

Like mentioned in the above screenshot which was taken from the course website, the error thrown by the app does not specify the reason for the bug and so can be considered as a FeatureFlaw. Furthermore, the team cannot assume that the user will always be above the "average population intelligence".

Hence, I think this is a bug that needs to be fixed.


## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** The team has not given a reason for why the severity is VeryLow and not Low Furthermore, the severity is not VeryLow as this is not a cosmetic bug. ![image.png](https://raw.githubusercontent.com/vibes-863/pe/main/files/fae0bf02-a2ed-40a3-9e2f-30cf83738d90.png) The above information has been screenshotted from the website.