Even long-standing, respected, professional testers will tell you: this is art more than science.
My trick for developing new test cases starts with the different types of tests you mentioned, and it should include all those that need to be thorough, but I'm trying to find a list of all the ways to interact with the code / product.
For an example of a vending machine, there are tons of parts inside and out.
Simple testing, as the product is designed to work, gives many cases
- This gives the correct changes.
- How fast does it process the request
- What to do if the product is missing.
- What to do if it is full.
- What to do if the change box is full.
- What to do if the elements are too large or badly broken.
- , .
- , .
, .
, , , " " , , , . , , , , /, - .
, , , / .
, , , .
, , . , , / , . , . , - ( ).
- , . -. , , . .
-, , , ( !), , . , , .
-, , , . , " ". , .
, , - "?", , , .
:
Q: ?
A: .
Q: ?
A: - , .
Q: ?
A: , , , .
Q: , , ?
A: : :
Q: : thing:?
A: : xyz:
Q: : xyz:
A: , : abc:
Q: : xyz: : abc:?
:... .
Q: ?
A:... , , ! , ?
, "" , . .
, , dev, pm, . , , .
, , - . , , , , , , . , ( ) .