Fundamentals of Testing

Core testing concepts including test objectives, testing principles, test activities, testware, test roles, and essential skills for effective testing.

5 minutes 5 Questions

The Fundamentals of Testing is a core section in ISTQB CTFL that establishes essential concepts and principles of software testing. It provides the foundation for understanding why testing matters and how it should be approached systematically. Why Testing Matters: Testing is a critical activity t…

Concepts covered
Test ObjectivesTesting and DebuggingTesting's Contributions to SuccessTesting and Quality Assurance (QA)Errors, Defects, Failures, and Root CausesSeven Testing PrinciplesTest Activities and TasksTest Process in ContextTestwareTraceability between Test Basis and TestwareRoles in TestingGeneric Skills Required for TestingWhole Team ApproachIndependence of Testing
Test mode:
Start practice test

CTFL - Fundamentals of Testing Example Questions

Test your knowledge of Fundamentals of Testing

Question 1

A team is developing a new mobile banking app. During the project, testers found several critical defects in the payment processing module before the app was released. The project manager asks: 'How did testing contribute to the success of this project?' Which answer best describes testing's contribution in this scenario?

Correct Answer: Testing helped identify defects before release, reducing the risk of failures in production

Testing's primary contribution to project success is identifying defects before release, which reduces the risk of failures occurring in the production environment and potentially causing harm to users or the business.

Writing better code is a development activity, not a testing activity. Testing complements reviews and static analysis but does not replace them; these are different and complementary quality assurance techniques. Claiming all defects were found and eliminated is incorrect because exhaustive testing is impossible, and testing can never guarantee the absence of all defects, only reduce the likelihood of failures.

The key concept tested is understanding how testing contributes to software project success by reducing risk through early defect detection.

Question 2

A tester finds that clicking 'Save' on a form causes the application to display an error message instead of saving the data. The tester logs this as a defect. A developer then examines the code and discovers a missing null check in the save function. The developer adds the null check and the defect no longer occurs. What best describes what the developer did after the tester logged the defect?

Correct Answer: The developer performed debugging by locating and fixing the cause of the failure

The developer examined the code to locate the root cause (a missing null check) and then fixed it, which is precisely the definition of debugging: identifying and removing the cause of a failure.

Testing involves executing software to find failures, not fixing code. Confirmation testing refers to re-running the original failed test case after the fix to verify the defect is resolved, which is a tester activity not described here. Regression testing involves checking that the fix did not introduce new defects in other areas, which is also not what the developer did in this scenario.

The key concept tested is the distinction between testing and debugging as defined in ISTQB.

Question 3

A team is testing an online food delivery app. A junior tester asks why the test strategy for this project differs significantly from the strategy used for a previous embedded medical device project, even though both projects are similar in size and budget. Which testing principle best explains why the team leader chose a different approach?

Correct Answer: Testing is context dependent, meaning the approach must be tailored to the specific characteristics of each project

Testing is context dependent is the correct principle because it directly states that testing approaches differ based on the context of the project, such as the domain, risk profile, regulatory requirements, and technology, which clearly explains why a food delivery app and a medical device require fundamentally different strategies despite similar size and budget.

Defect clustering relates to where defects concentrate within a system, not why entire strategies differ across projects. Early testing is about when testing begins in the lifecycle, not about why strategies differ between domains. Exhaustive testing being impossible addresses test coverage limitations, not the rationale for tailoring strategies to different project contexts.

Key concept tested: ISTQB Principle 7, Testing is context dependent.

More Fundamentals of Testing questions
795 questions (total)
Practice 100 questions
One session at a time, always new questions