4.4 Experience-based Test Techniques Flashcards
What is error guessing in software testing?
Error guessing involves anticipating errors, defects, and failures based on the tester’s knowledge and experience with the application, past errors made by developers, and failures in similar applications.
What are Fault Attacks in Error Guessing?
Fault attacks in error guessing require testers to create or acquire lists of possible errors, defects, and failures to design tests that expose defects associated with these errors or cause failures, based on experience and common knowledge.
What is exploratory testing and how is it conducted?
Exploratory testing involves simultaneously designing, executing, and evaluating tests while learning about the test object. It often uses session-based testing within a defined time-box, guided by test charters and followed by debriefings to discuss test results.
In what scenarios is exploratory testing particularly useful?
Exploratory testing is useful when there are inadequate specifications, time constraints, or a need to complement formal test techniques. It is more effective with experienced testers possessing domain knowledge and essential skills.
What is checklist-based testing?
Checklist-based testing involves designing, implementing, and executing tests based on predefined checklists that cover test conditions derived from experience, user needs, or understanding of software failure reasons.
How are checklist items typically structured in checklist-based testing?
Checklist items are often phrased as questions that can be checked separately and directly. They cover various test conditions such as requirements, graphical interface properties, or quality characteristics.
Why is it important to update checklists regularly in software testing?
Checklists should be updated regularly based on defect analysis to reflect new high-severity defects and to adapt as developers learn to avoid previous errors. However, they should be managed to prevent becoming overly lengthy.
What drawback might arise from using high-level checklists in software testing?
High-level checklists may result in variability in actual testing approaches, potentially leading to greater coverage but less repeatability in test outcomes.
