A team is debating whether to perform static testing on their legacy codebase, which is poorly documented and has no existing tests. The team is concerned about the time investment. What is the most compelling reason to proceed with static testing?

Static testing is required by law for all legacy code.

Static testing is faster than dynamic testing, so it will save time immediately.

Static testing can identify defects and improve maintainability, reducing future rework and increasing confidence in the codebase.

Static testing will automatically fix all defects in the legacy code.

A project manager is deciding when to introduce static testing into the development lifecycle. The team has a tight budget and wants to minimize the total cost of quality. When should static testing be performed to achieve the greatest cost benefit?

During system testing, alongside performance testing

As early as possible, starting with requirements and design documents

Only after the code is complete and all dynamic tests have passed

Only when a defect is reported by a customer

A tester is asked to find defects in a system that is not yet executable. Which of the following activities would be most appropriate?

Executing unit tests on the code

Running load tests to measure system performance

Reviewing the requirements and design documents for inconsistencies

Performing exploratory testing on the user interface

Which of the following is a typical defect that static testing can identify in requirements documents?

A security breach that occurs due to a missing authentication check

A performance degradation when the system handles a large number of users

A requirement that is ambiguous and can be interpreted in multiple ways

A runtime exception that occurs when a user enters invalid data

Certified Tester Foundation Level

Domain 3Objective 2

Value of Static Testing CTFL Practice Questions (Page 5)

Part of the Domain 3: Static Testing domain, which makes up ~31% of our current practice bank. ISTQB does not publish an official question count, but from its 60-minute exam (~25–40 total, ~8–12 in this domain), expect 1–2 from this objective — we provide 24 practice questions to prepare you well beyond it. (estimate)

24questions here

5free pages

5concepts

Questions 21–24

21expert · hard
A team is debating whether to perform static testing on their legacy codebase, which is poorly documented and has no existing tests. The team is concerned about the time investment. What is the most compelling reason to proceed with static testing?
Select an answer first
22application · medium
A project manager is deciding when to introduce static testing into the development lifecycle. The team has a tight budget and wants to minimize the total cost of quality. When should static testing be performed to achieve the greatest cost benefit?
Select an answer first
23application · medium
A tester is asked to find defects in a system that is not yet executable. Which of the following activities would be most appropriate?
Select an answer first
24foundation · easy
Which of the following is a typical defect that static testing can identify in requirements documents?
Select an answer first

Finished these 4 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack to CTFL

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTFL” is a trademark of its owner, used for identification only.