Foundation Level ISTQB-CTFL Book

The key difference between the mindsets for test activities and development activities lies in the objectives: a tester is primarily concerned with finding defects to ensure product quality, while a developer focuses on designing and building solutions. This distinct focus helps ensure thorough quality checks and balances within the software development life cycle​ (ISTQB not-for-profit association)​.

Matching the main review process activities with the specific review activities, we see that planning includes estimating effort and timeframe (2) and selecting people to participate (4). Initiating a review involves distributing work products and other material (5). Issue communication and analysis includes evaluating the review findings (6). Fixing and reporting would entail creating defect reports (1) and recording the updated status of defects (3).

Static testing involves reviewing and inspecting the code, requirements, or design documents without executing the code. It can prevent defects, is effective early in the software development life cycle, and can help eliminate defects in user stories.

Option 1: "It can prevent defects by manual examination of the functional specification" - This is a value of static testing.

Option 2: "It is effective since it can be performed very early in the software development life cycle" - This is a value of static testing.

Option 3: "It can detect the failures in the running application" - This is a v​ (ISTQB not-for-profit association)​namic testing, not static testing.

Option 4: "It can help eliminate defects in user stories" - This is a value of static testing.

Option 5: "It can verify externally visible behaviors" - This is a value of dynamic testing, not static testing.

Therefore, the correct set of statements representing values only for static testing is 1, 2, 4, which corresponds to answer C【6†source】.

When working on a project with incomplete requirements and under pressure to deploy, exploratory testing is particularly suitable. This type of testing allows testers to use their expertise and intuition to explore the system's functionality and identify defects without needing detailed specifications. Exploratory testing is flexible and can quickly adapt to changes and gaps in the requirements​​.