Open delishad21 opened 4 months ago
We see that we haven't provided enough explanation in the DG regarding the testing of the other commands, however the developers can technically still test out the other commands. Furthermore we would categorize this as a low severity since this is a flaw that is unlikely to affect normal operations of the product.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: I agree that the lack of manual testing instructions does not impact normal operations of the application. However, for a documentation error, we are referring to inconveniences to the reader, who in the context of the manual testing section, is a developer wishing to test the application. Considering that the manual testing only included two tests, both of which was not even part of any of the new features that the team has implemented, shows a clear lack of effort in documentation.
This causes great inconvenience to the readers of the guide, who then have to draft up their own test cases to test the functionality of the application. Furthermore, as the implementation of certain new functionality (phone copying/ tagging and untagging) was not even documented under any other section in the DG, It limits testers to only black box testing which severely inhibits the extent to which developers can test the application. Considering all these factors, this documentation issue at the very least a medium severity one, if not high.
On a separate note, this manual testing section does not even meet the course requirements, which state that all user-testable features (excluding AB3 features) should be covered under the manual testing section.
There are clearly insufficient manual testing instructions in the developer guide. It only includes deleting and saving of data. It also looks incomplete. as there are portions with "{more test cases ...} included. This is a massive inconvenience for any developer wanting to test out the application.