menatahari / pe

0 stars 0 forks source link

Missing Information On Instructions for Manual Testing in Developer Guide #5

Open menatahari opened 2 months ago

menatahari commented 2 months ago

There are barely any test cases aside from delete person in the instructions for manual testing. All other commands don't have any instructions, and the { more test cases… } is still visible in the developer guide, suggesting that the developer guide is not yet final for the reader and more things should be added.

Screenshot 2024-04-19 at 17.20.14.png

nus-pe-script commented 2 months ago

Team's Response

I believe that this issue should be lowered to a severity of medium. Our application is still manually testable without detailed instructions on every command implemented.

Items for the Tester to Verify

:question: Issue severity

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

Reason for disagreement: I believe the developer team's reason for lowering the severity is invalid. It is true that the system is still manually testable without the section, but that's relying only on the UG, not DG. If the readers are going solely from reading the DG, there's no way to test the correct behavior of the product with this section gone.

Because of this missing section, there is no way to know what the exact expected behavior of the app is when we input valid or invalid commands, and we have no basis for knowing whether the app is actually giving out the expected behavior as we can only guess the behavior from the UG and even then, it is not detailed enough to cover all cases, for example, the UG mentioned that the efficiency score will drop when the asignee completed the task later than the deadline. But when the assignee's efficiency is 0% the efficiency stays at 0 and doesn't drop; this kind of case is not explained anywhere in the guides and can cause confusion. Same thing happens with the result of the find command, where find a will list out all employee with tag and industry containing the letter a anywhere within the word and the expected behavior is not explained anywhere.

It might seem obvious to the developer team, but it is not as obvious to the reader, and omitting almost all of the commands from the manual testing instructions is majorly hindering the readers. And, according to the guide in determining the severity, I believe this missing section will affect most readers and cause major inconvenience for most, hence the high severity. Screenshot 2024-04-25 at 23.37.49.png