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

Not Enough Manual Testing Test Cases #6

Open
KhoonSun47 opened this issue Apr 19, 2024 · 1 comment
Open

Not Enough Manual Testing Test Cases #6

KhoonSun47 opened this issue Apr 19, 2024 · 1 comment

Comments

@KhoonSun47
Copy link
Owner

KhoonSun47 commented Apr 19, 2024

Not enough manual test cases in the DG for testing (the current command that can be tested is only the saving into storage and the delete command)

image.png

Suggestion: I believe that there should be sufficient test cases in the DG to cover all the commands, just like in the UG.

@nus-se-script
Copy link

nus-se-script commented Apr 22, 2024

Team's Response

Thanks for bringing up the issue. We think it is a good to have but does not hinder the user or tester from trying out the examples already provided in the UG and DG.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

  • I disagree

Reason for disagreement: I disagree with the classification of this response as "response.NotInScope," and I believe it should be revised to "response.Accepted" instead. 


The website explicitly states that the manual testing instructions must guide the tester through the application's features, which extend beyond deleting, launching, and shutting down. This application itself has other features that can be tested such as add, find, filter and etc...

It also specifies that the instructions should provide essential test inputs to facilitate direct application by the tester.

Pasted Graphic.png

image.png


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