Software Testing Techniques Quiz

What is the purpose of a reading technique in static testing?

• To guide an inspector to acquire a deep understanding of the inspected product

• To execute the software to find bugs

• To create test cases for dynamic testing

• To perform performance analysis

Which method relies entirely on the inspector's skills, knowledge, and experience?

• Checklist

• Ad hoc method

• Scenario-based reading

• Perspective-based reading

What is a major drawback of using checklists in static testing?

• They are too specific

• They often miss defects not previously detected

• They are always customized to the development environment

• They provide too much guidance

What type of reading technique provides more specific instructions than typical checklists?

• Ad hoc method

• Scenario-based reading

• Abstraction driven reading

• Usage-based reading

In which reading technique does an inspector check software from different stakeholder perspectives?

• Perspective-based reading

• Usage-based reading

• Abstraction driven reading

• Task-driven reading

Which reading technique is specifically designed for code inspections by abstracting functions?

• Scenario-based reading

• Abstraction driven reading

• Task-driven reading

• Function-point based scenarios

What is the focus of usage-based reading?

• Finding defects based on scenarios

• Abstracting code functions

• Inspecting design documentation based on use cases

• Creating a data dictionary

Which reading technique involves creating a data dictionary and a cross-reference between code and specifications?

• Abstraction driven reading

• Task-driven reading

• Perspective-based reading

• Function-point based scenarios

What is the primary focus of function-point based scenarios?

• Functional defects relevant to users

• Abstracting code functions

• Reviewing documentation from different perspectives

• Defect detection in requirements documents

What is a key feature of structured walkthroughs compared to inspections?

• They are more formal and rigorous

• They use checklists to guide the process

• They are less formal and do not use checklists

• They involve extensive documentation