search

nus-cs2103-AY2324S2 / forum

16 stars 0 forks source link

A Tricky Tester Response Scenario #938

Closed benson1029 closed 6 months ago

benson1029 commented 6 months ago

I will be using variables below for simplicity.

I tested commands A and B during the PE and they have inconsistent behaviours with each other. According to my judgement, command A has the correct behavior while command B doesn't. I proceeded to report the incorrect output of command B under type.FunctionalityBug (without mentioning command A at all).

However, now that the dev team argued that command B has the correct behaviour (which implies command A doesn't). It is possible to argue that the behaviour is consistent with the user guide (with ambiguity), while it clearly contradicts with the user stories in the DG.

What should I do in the tester response phase?

Action 1: Forgo the bug since I did not mention command A in the bug report. Action 2: Continue arguing that command B has an incorrect behaviour. (i.e. disagree with the rejection) Action 3: Adopt the team's logic but state that command B has a severe feature flaw. Action 4: Report an issue with documentation.

All of Actions 2, 3 and 4 seem weird to me (and I'm not sure whether they are allowed), but choosing Action 1 means that there is a loophole in the PE which allows teams to get away with serious bugs (rather easily).

May someone advise for this? Thanks!

aureliony commented 6 months ago

It would be better if you could provide additional context (i.e., provide a link to the issue)

benson1029 commented 6 months ago

It would be better if you could provide additional context (i.e., provide a link to the issue)

I will be providing a link after the developer response phase is over, if the issue is still under discussion by then.

benson1029 commented 6 months ago

Moving to #955