Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find Command lacking a few important test cases #5776

Open
nus-pe-bot opened this issue Nov 11, 2022 · 1 comment
Open

Find Command lacking a few important test cases #5776

nus-pe-bot opened this issue Nov 11, 2022 · 1 comment

Comments

@nus-pe-bot
Copy link

nus-pe-bot commented Nov 11, 2022

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.



image.png

Find command requires -all or -any for tags, and if it doesn't it throws an error. However there are no test cases for this and developers may not know what to expect.


[original: nus-cs2103-AY2223S1/pe-interim#5765] [original labels: type.DocumentationBug severity.Low]
@seelengxd
Copy link
Contributor

Team's Response

Extract from CS2103T website: DG - manual testing section

No need to give a long list of test cases including all possible variations. It is up to the tester to come up with those variations.
Information in this appendix should complement the UG. Minimize repeating information that are already mentioned in the UG.

The developer can go to our UG, to see the other find command variations.

Duplicate status (if any):

--

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants