CTFL
Free CTFL practice questions
10 questions from our CTFL practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Fundamentals of Testing
A team keeps running the same regression suite every sprint. For several releases it has found no new defects, although users still report problems in recently changed areas. Which testing principle BEST explains this situation?
- AAbsence-of-defects fallacy
- BDefects cluster together
- CTesting is context dependent
- DTests wear out Correct answer
Answer and explanation: Tests wear out (formerly the pesticide paradox): repeating identical tests becomes less effective at finding new defects, so tests and test data need to be modified or new tests written. Defect clustering is about defects concentrating in a few components, the absence-of-defects fallacy is about a defect-free system still failing user needs, and context dependence is about tailoring testing to the situation.
Question 2 of 10, Fundamentals of Testing
How do the typical mindsets of testers and developers differ, according to the CTFL syllabus?
- ABoth mindsets are identical, so developers can always test their own code with the same effectiveness
- BDevelopers are focused on designing and building solutions, while testers focus on verifying and validating the product Correct answer
- CDevelopers focus on user needs only, while testers focus on technical implementation details only
- DTesters are focused on building solutions quickly, while developers are focused on finding defects in the work of others
Answer and explanation: Developers are often more interested in designing and building solutions than in contemplating what might be wrong, while testers bring curiosity, professional pessimism and attention to detail to verifying and validating. The roles are not reversed, the mindsets differ (which is why authors miss their own defects), and neither group is limited to one perspective.
Question 3 of 10, Testing Throughout the Software Development Lifecycle
Which practice is an example of shift left?
- ARunning acceptance tests only after the complete system has been released to production
- BUsing CI/CD with automated component tests to get fast feedback on each change Correct answer
- CExecuting exploratory tests in production instead of reviewing the specification beforehand
- DPostponing all non-functional testing until a dedicated test phase at the end of the project
Answer and explanation: Shift left means testing earlier in the SDLC; examples include reviewing specifications, writing tests before code, CI/CD with automated component tests, static analysis before dynamic testing, and non-functional testing at component level where possible. Postponing non-functional tests, running acceptance tests only after release, and replacing specification reviews with production exploration all move testing later.
Question 4 of 10, Testing Throughout the Software Development Lifecycle
Which is a RISK or challenge of DevOps that the CTFL syllabus mentions for testing?
- ANon-functional characteristics become less visible because they are only measured in production
- BThe delivery pipeline must be defined and set up, and CI/CD tools must be maintained Correct answer
- CManual testing from the user's perspective becomes impossible once the pipeline is automated
- DDevelopers can no longer write component tests because the pipeline executes only system tests
Answer and explanation: Listed challenges are that the DevOps delivery pipeline must be defined and established, CI/CD tools must be introduced and maintained, and test automation requires additional resources and may be hard to set up. Manual testing remains possible and needed, DevOps increases visibility of non-functional characteristics, and component tests are typically part of the pipeline.
Question 5 of 10, Static Testing
A team must decide quickly on the technical approach for a new database design and gain agreement among architects. Which review type is MOST suitable?
- AWalkthrough
- BInspection
- CInformal review
- DTechnical review Correct answer
Answer and explanation: A technical review is performed by technically qualified reviewers led by a moderator, with objectives such as gaining consensus and making decisions on technical problems. Informal reviews lack structure for decisions, walkthroughs are author-led and focus on education or consensus more generally, and inspections are heavyweight and focused on finding the maximum number of anomalies.
Question 6 of 10, Test Analysis and Design
Which statement about checklist-based testing is correct according to the CTFL syllabus?
- AChecklists must be fixed for the lifetime of a product so that results are comparable
- BChecklist-based testing cannot be used for non-functional quality characteristics
- CChecklist items are always formulated as detailed step-by-step test procedures
- DChecklists should not include items that can be checked automatically or that are too general Correct answer
Answer and explanation: The syllabus states that checklists should not contain items that can be checked automatically, items better suited as entry or exit criteria, or items that are too general; they need regular updates based on defect analysis. Freezing checklists lets them become less effective, items are questions or conditions rather than procedures, and checklists can support non-functional testing such as usability.
Question 7 of 10, Test Analysis and Design
A team found that formal test cases missed several usability problems that users later reported. The product has short iterations and incomplete specifications. Which technique would BEST complement their existing tests?
- AAdditional boundary value analysis on numeric fields
- BStatement testing on the user interface code
- CExploratory testing by testers with domain knowledge Correct answer
- DStrictly scripted regression tests with fixed data
Answer and explanation: Exploratory testing is effective when specifications are incomplete and time is short, and it complements formal techniques by finding problems scripted tests miss, especially with skilled, domain-knowledgeable testers. Statement testing measures code coverage, BVA targets numeric edges, and more scripted regression tests are unlikely to uncover new usability issues.
Question 8 of 10, Test Analysis and Design
An experienced tester designs tests by anticipating the defects developers are likely to make, based on past failures in similar applications. Which technique is this?
- AChecklist-based testing
- BBoundary value analysis
- CExploratory testing
- DError guessing Correct answer
Answer and explanation: Error guessing anticipates errors, defects and failures based on the tester's knowledge, such as how the application worked before and typical developer mistakes. Exploratory testing designs and executes tests simultaneously while learning, checklist-based testing uses a list of test conditions, and BVA is a black-box technique based on partition edges.
Question 9 of 10, Managing the Test Activities
A test manager orders the regression tests so that each next test adds the most coverage not yet achieved by the tests already selected. Which prioritization strategy is this?
- AAdditional coverage prioritization Correct answer
- BRisk-based prioritization
- CRequirements-based prioritization
- DPlanning poker prioritization
Answer and explanation: Coverage-based prioritization orders tests by coverage, and its variant additional coverage prioritization first picks the test with highest coverage and then each test adding the most extra coverage. Risk-based ordering uses risk analysis results, requirements-based ordering uses requirement priorities from stakeholders, and planning poker is an estimation technique.
Question 10 of 10, Managing the Test Activities
A test manager must report status to two audiences: the development team needs daily detail, and senior management wants a monthly overview. Which approach is MOST appropriate?
- AReport only at test completion, to avoid influencing stakeholders during the project
- BSend the same detailed daily defect list to everyone so that all stakeholders get identical information
- CTailor it: frequent updates or dashboards for the team, summarized formal reports for management Correct answer
- DReport only to senior management, because the team can read the defect tool themselves
Answer and explanation: Test reports should be tailored to the audience; the syllabus lists options such as verbal communication, dashboards, electronic channels and formal documentation chosen by stakeholder needs. Identical detailed reports overwhelm management, ignoring the team reduces collaboration, and waiting until completion denies timely information for control.