ISTQB FOUNDATION 4.0 | Tutorial 39

What is a checklist in software testing?

• A list of items that can be checked automatically

• A questionnaire consisting of questions about a product

• A detailed test case for each functionality

• A document containing entry and exit criteria

What is the purpose of a checklist in dynamic testing?

• To automate the testing process

• To ensure all requirements are met

• To define detailed test cases

• To validate the product functionalities

Why should checklist items be phrased in the form of questions?

• To ensure direct and separate checking of each item

• To increase the length of the checklist

• To make it difficult to check each item separately

• To confuse the testers

What is the drawback of using checklist in software testing?

• They are only applicable for functional testing

• They are difficult to create

• They are not time to time updated

• They are too detailed

How often should a checklist be updated according to the text?

• Never

• Once a year

• Every 5 years

• Regularly based on defect analysis

What is the main purpose of checklist-based testing?

• To provide guidelines and consistency for testing

• To automate the testing process

• To replace detailed test cases

• To increase the length of test documentation

What is the potential drawback of having high-level checklists?

• Improved coverage measurement

• Increased automation in testing

• More detailed test cases

• Less repeatability in testing

What is the role of a tester in designing a checklist?

• To base it on experience and knowledge

• To include all possible test cases

• To make it as detailed as possible

• To automate the checklist creation

Why should checklist items not include things that can be checked automatically?

• To avoid redundancy with automation

• To ensure manual testing is required

• To make the checklist shorter

• To confuse the testers

What is the importance of updating checklist entries over time?

• To increase the length of the checklist

• To reflect newly found defects

• To confuse the testers

• To avoid using checklists