search

tianyue58 / pe

0 stars 0 forks source link

Inconsistency in use case #13

Open tianyue58 opened 2 years ago

tianyue58 commented 2 years ago

For extension 3a in the two screenshots, there should be some consistency on where the use case resume.

Screenshot 2021-11-12 at 5.27.19 PM.png

Screenshot 2021-11-12 at 5.27.02 PM.png

nus-pe-bot commented 2 years ago

Team's Response

Labeled as not in scope.

Both variations are fine as they both makes sense. I do not think inconsistency is a bug.

Also downgraded from Medium -> VeryLow.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: Arguably, when there is an error occurred, the program could be considered to resume at either at showing the list or user request step. However, it could be confusing to users if in the use case, under similar circumstances, there is inconsistency on where the use case should resume. Hence, I believe this should be considered as a bug and it is within scope.

:question: Issue severity

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

Reason for disagreement: I disagree with the downgrading of severity to VeryLow. However, I admit I may be a little harsh during PE and I think I would change the severity level to Low instead.

The rationale for my choice of severity level is as follows.

Firstly, on the website, only purely cosmetic flaw can be of level VeryLow, but this bug involves logic. Secondly, the inconsistency does cause confusion to users and occurs more than once in the use cases.