ISTQB Study Centre

ISTQB Exam Question Paper, Part 2 11 Consider the following statements i. an incident may be closed without being fixed ii. incidents may not be raised against documentation iii. the final stage of incident tracking is fixing iv. the incident record does not include information on test environments v. incidents should be raised when someone other than the author of the software performs the test a) ii and v are true, I, iii and iv are false b) i and v are true, ii, iii and iv are false c) i, iv and v are true, ii and iii are false d) i and ii are true, iii, iv and v are false e) i is true, ii, iii, iv and v are false 12 Given the following code, which is true about the minimum number of test cases required for full statement and branch coverage: Read P Read Q IF P+Q > 100 THEN Print “Large” ENDIF If P > 50 THEN Print “P Large” ENDIF a) 1 test for statement coverage, 3 for branch coverage b) 1 test for statement coverage, 2 for branch coverage c) 1 ...

A walkthrough is a review technique in software testing where the author of a work product (such as requirements, designs, test cases, or code) leads a group of peers through the material to build shared understanding and uncover potential defects early. Key Features of a Walkthrough Author‑led session The creator guides participants through the document or artefact, explaining logic, intent, and decisions. Use of scenarios and dry runs The group may step through example workflows or test scenarios to validate completeness and accuracy. Peer‑group discussion Walkthroughs encourage open, exploratory conversation, allowing reviewers to ask questions, challenge assumptions, and highlight risks. Optional preparation and documentation Depending on the level of formality, the session may include: Pre‑reading by reviewers A structured review report A list of findings A scribe to capture actions and observations Formality Levels Walkthroughs can range from informal knowledge‑shar...