4.4.3 Checklist-Based Testing Flashcards
In checklist-based testing, a tester “ “, “ “, and e… to cover t… from a “ “.
designs
implements
executes tests
test conditions
checklist
Checklists can be built based on “e…“, “k…“ about what is important for the “ “ or an understanding of “ “ and how s…
experience
knowledge
user
why
software fails.
Checklists should not contain items that can be checked “ “, items better suited as e… , or items that are too “ “.
automatically
entry criteria / exit criteria
general
Checklist items are often phrased in the form of a “ “.
question
It should be possible to check each item s…
separately and directly.
These items may refer to:
- re…
- graphical in…
- qua…
- non-f… (10 heuristics for …
- requirements
- interface properties
- quality characteristics
- non-functional testing
usability testing).
Some checklists entries may gradually become less e… because the developers will learn to avoid m…
effective over time
making the same errors.
New entries may also need to be added to reflect newly found h…
high severity defects.
Checklists should be regularly updated based on d…
However, care should be taken to avoid letting the checklist become t…
defect analysis,
too long.
In the absence of detailed test cases, checklist-based testing can provide some “ “ and some degree of t… for the “ “.
guidelines
test consistency
testing.
If the checklists are high-level, some variability in the actual testing is …
likely to occur, resulting in potentially greater coverage but less repeatability.