teoziyiivy / pe

0 stars 0 forks source link

Current cap can be longer than 2 decimal places but expected cap is only to 2 decimal places despite recurring number. #7

Open teoziyiivy opened 3 years ago

teoziyiivy commented 3 years ago

image.png

nus-pe-bot commented 3 years ago

Team's Response

The current cap is provided by the user. We formatted the expected CAP based on the system that NUS is using (2 decimal places)

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: As stated below, I believe that this is a scenario where a legitimate user behaviour is not handled. image.png

In this scenario, it would be better to limit the user input to 2 decimal places as well. Since this limitation is not listed in your UG/DG, that the expected CAP is limited to only 2 decimal places, users will be confused as to why they can input to a larger decimal place but unable to view their expected CAP to a decimal place larger than 2. Many alternatives to your application online allows for longer recurring outputs with a simple implementation of rounding towards the end which provides a more accurate calculation of expected CAP. As shown below:

image.png