Open jannaleong opened 4 months ago
Thank you for the response, this is a valid concern. We accept that we missed out testing instructions for the cluster command. However, this function still can be tested even without such a section, with sufficient information given throughout the guide. The command word can be found in the cluster command implementation of the developer guide, while the error message shown on the app gives indication on the command function and appropriate inputs to the app. Hence we changed the severity from medium to low.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: By the definition of low severity, it is something that "Appears only in very rare situations and causes a minor inconvenience only."
However, as this is the manual testing section, almost all your testers or future developers of your app will be looking at your manual testing section to ensure that all your commands work as expected and they did not install a faulty program. This, after all, is a key reason why you have a manual testing section in the first place. They will then realise that the cluster feature is missing and by referring to only your testing guide, they will not be able to test this section.
This is not a very rare situation as it is a problem almost all your testers and future developers will encounter.
Rather, then being a very rare inconvenience, it causes occasional inconvenience to some users. You are right in pointing out that readers could look at other parts of your developer guide and come up with their own tests. But this already causes inconvenience to the users as they have to come up with their own tests. Following the definition that medium severity bugs causes "occasional inconvenience to some users", as this bug causes inconvenience to at least some users, it is medium severity.
Manual testing section does not include cluster feature.
This is problematic as developers who want to test if the products works on their system are unable to test this command.