ISTQB CTFL

White-box, experience-based and collaborative approaches

60 questions

Easy

White-box test techniques

  1. What are the coverage items in statement testing?
  2. What does 100% statement coverage guarantee?
  3. What is a branch in the sense of branch testing?
  4. What is the relationship between branch and statement coverage?
  5. What strength do white-box techniques have?

Experience-based test techniques

  1. What is error guessing based on?
  2. What is a fault attack?
  3. What characterises exploratory testing?
  4. What does a test charter contain in session-based testing?
  5. How are checklist items often phrased?
  6. What should a checklist not contain?
  7. When is exploratory testing particularly useful?

Collaboration-based test approaches

  1. What do the "3 C's" of a user story stand for?
  2. What is the usual format of a user story?
  3. What does the T in INVEST stand for?
  4. What are the acceptance criteria of a user story?
  5. Which two formats for acceptance criteria are most common?
  6. What does ATDD start with?
  7. Which test cases are typically created first in ATDD?
  8. What is one purpose of acceptance criteria?

Medium

White-box test techniques

  1. Which defects does a test with 100% statement coverage not necessarily find?
  2. How is statement coverage calculated?
  3. Which are examples of conditional branches?
  4. Which defects does 100% branch coverage not necessarily find?
  5. Which statements about the value of white-box testing are correct?

Experience-based test techniques

  1. Which areas does error guessing typically target?
  2. Where can lists for fault attacks come from?
  3. Which elements does session-based exploratory testing have?
  4. Which statements about exploratory testing are correct?
  5. Why should checklists be updated regularly?
  6. What is a consequence of high-level checklists?
  7. Which tester qualities make exploratory testing particularly effective?

Collaboration-based test approaches

  1. Which perspectives are brought together in collaborative user story writing?
  2. A stakeholder has no idea how a user story could be tested. What might that indicate?
  3. Which purposes do acceptance criteria serve?
  4. May a team use its own format for acceptance criteria?
  5. In which order are test cases typically developed in ATDD?
  6. Which statements about ATDD test cases are correct?
  7. What do ATDD test cases become when captured in a format supported by an automation framework?
  8. How do collaborative approaches differ from the other test techniques?

Hard

White-box test techniques

  1. A function contains two independent decisions without else branches: "if voucher, then lower price" followed by "if new customer, then send welcome mail". What is the minimum number of test cases for 100% statement coverage?
  2. For the same function with the two independent decisions without else branches, 100% branch coverage is to be achieved. What is the minimum number of test cases?
  3. Code: "if member, then (if turnover > 1000, then discount 10% else discount 5%) else no discount". What is the minimum number of test cases for 100% branch coverage?
  4. A function "if quantity > 0, then price = total / quantity" is tested with quantity 4 and reaches 100% statement coverage. Later it crashes because the condition in the code wrongly reads "quantity >= 0". Which statements are correct?
  5. A requirement calls for an age check when buying energy drinks, but the developers forgot it. The tests achieve 100% branch coverage. What does this case show?
  6. A test suite achieves 100% statement coverage but only 70% branch coverage. Which statements are possible?
  7. A developer walks through a function that does not run yet on paper using its control flow graph to see whether every branch is reachable. How should this be classified?
  8. The control flow graph of a function has 12 branches, 4 of them unconditional. The tests exercise all unconditional branches and 5 of the conditional ones. What is the branch coverage?

Experience-based test techniques

  1. A tester knows that similar forms had problems with umlauts in names, very long email addresses and double submission, and tests exactly these cases. Which technique is she using?
  2. There are hardly any requirements for a new photo editing app, and the release is in three days. Which approach fits best?
  3. After a 90-minute exploratory session the tester discusses his findings with the product owner and developer. Which statements are correct?
  4. A team checks a website's usability against a list of recognised heuristics. Which statements are correct?
  5. A checklist for code checks contains: "Does the build run without warnings?", "Is the software good?" and "Are all inputs checked for length?". Which items are unsuitable?
  6. Why do experience-based techniques complement black-box and white-box techniques?
  7. A team plans a 60-minute exploratory session on the returns feature of an online shop. What belongs in the test charter?

Collaboration-based test approaches

  1. Which acceptance criteria are written in a rule-oriented way?
  2. The story "As a user I want the whole portal to become faster and nicer" is discussed in refinement. Which INVEST properties does it violate most clearly?
  3. A team uses ATDD to develop the story "customer can book a garage appointment online". Which steps match the approach?
  4. In ATDD test cases are written for a story. Which test techniques may be used?
  5. Which assignment to the "3 C's" is correct for a story on a digital board?

Certifications & exams

Which exam comes next?

You can already practise for 51 exams, and 16 are up for a vote. See all certifications with their official information, cast your vote or suggest your exam.

See all certifications