Free CTFL sample questions

Correct answer: It follows a defined process with entry/exit criteria, formal roles, and metrics collection.

Inspections are the most formal type of review. They are characterized by a rigorously defined process, specified entry and exit criteria, formal roles (like Moderator, Scribe, Reviewer), and the collection of metrics to improve both the product and the review process itself. The author does not lead the meeting, and the primary goal is defect detection, not brainstorming.

Correct answer: Unrealistic expectations that automation will find all defects without manual intervention.

A major risk in test automation is setting unrealistic expectations. Stakeholders may believe automation is a 'silver bullet' that replaces manual testing entirely and finds all bugs. In reality, automation is best for repetitive tasks like regression testing, but it requires significant investment in creation and maintenance, and it is not a substitute for the critical thinking and exploratory abilities of a manual tester.

Correct answer: Absence-of-errors fallacy.

The absence-of-errors fallacy states that finding and fixing a large number of defects does not guarantee the success of a system if the system itself does not meet user needs or is unusable. In this case, even though all specified requirements were tested and passed (absence of errors), the system was still unsafe because the requirements missed a critical real-world scenario. Verification (testing against requirements) was done, but validation (ensuring it's fit for purpose) failed.

Correct answer: Prepare a test completion report detailing the status, coverage metrics, and residual risks, and present this data to stakeholders for a formal risk acceptance decision.

The role of the test manager is not to unilaterally approve or block a release but to provide clear, data-driven information to stakeholders so they can make an informed business decision. The most professional and appropriate action is to communicate the exact testing status, including coverage of high-risk areas and the specific residual risks (open defects, untested areas). This allows stakeholders to formally accept the risk before proceeding.

Correct answers: A clear, concise title summarizing the failure.; A description of the actual result versus the expected result.; Detailed, step-by-step instructions to reproduce the failure.

A good title (e.g., 'Crash on file upload with >10MB PNG file') immediately informs the developer of the problem's nature and context.

Clearly stating what happened (actual result: 'Application crashes') versus what should have happened (expected result: 'File uploads successfully and a confirmation message appears') defines the failure and removes ambiguity.

This is the most critical part of a defect report. Without clear, repeatable steps, the developer may be unable to find, diagnose, or fix the bug.

Correct answer: Static testing, because the code is being analyzed without being executed.

Static testing involves examining work products (like source code) without executing them. Static analysis tools automate this process by checking the code against predefined rules and patterns to find potential defects, such as the null pointer exception mentioned. It is not dynamic testing because the code was not run.

Correct answer: False

This statement describes regression testing. The primary purpose of confirmation testing is to verify that the original reported defect has been successfully fixed. Regression testing is the separate activity performed to check for unintended side effects (new defects) in unchanged parts of the software.

Correct answer: The system may fail to secure customer data in compliance with privacy regulations.

Product risks are related to the quality and characteristics of the software itself (what it does). A failure to secure data is a quality issue inherent to the product. Project risks are related to the management and execution of the project (how it's built), such as staff leaving, budget cuts, or schedule delays.

Correct answer: Test conditions

A test condition is an item or event of a component or system that could be verified by one or more test cases. In the test analysis phase, high-level requirements are broken down into these more specific, testable conditions before detailed test cases (with steps and expected results) are designed.

Correct answer: Exploratory testing

Exploratory testing is an experience-based technique where the tester simultaneously learns about the system, designs tests, and executes them. It is particularly powerful when documentation is poor or missing, as it relies on the tester's skill, curiosity, and critical thinking to uncover defects that formal, specification-based techniques might miss.