CTFL-v4 Test Analysis and Design Practice Question
Which THREE of the following are considered 'test basis' documents used during Test Analysis and Design?
⚠ Common exam trap
Candidates often incorrectly include test plans, test logs, or incident reports as 'test basis' documents, forgetting that the basis consists of information used to derive the tests themselves.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
System requirements specifications
The test basis represents all information used to understand the software requirements and design constraints. Documents like risk analysis reports, system requirements specifications, and interface definitions are vital because they define the expected behavior of the system. Without a solid test basis, testers cannot define accurate test conditions or criteria, leading to a disconnect between the developed software and the actual business requirements, ultimately causing defects to persist into production.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
System requirements specifications
Why this is correct
Requirements specifications are the primary source of truth for system functionality. They define the intended features and behaviors that the test team must verify. Using these documents ensures that the test design is directly aligned with the agreed-upon business needs and functional objectives of the project.
- ✓
Risk analysis reports
Why this is correct
Risk analysis reports identify which areas of the system are most prone to failure or have the highest impact. Using these reports as a test basis allows testers to prioritize their design efforts effectively, ensuring that the most critical areas receive the most rigorous and comprehensive testing.
- ✗
The project budget plan
Why it's wrong here
The budget plan is an administrative document used for project management and resource allocation. It contains no information about the software's functional or non-functional requirements. Including it in the test basis would not assist in deriving test conditions or designing effective test scenarios for the application.
- ✓
Interface specifications
Why this is correct
Interface specifications define how the system communicates with external components or users. These are critical for designing integration tests and ensuring that data flows between systems are correct. They serve as a key basis for validating the technical interoperability of the software within its broader ecosystem.
- ✗
Previous test execution logs
Why it's wrong here
While useful for regression analysis, execution logs are historical data of past performance, not a definition of what the system should do. They are not considered a foundational test basis document for defining new test conditions, as they represent past results rather than current system requirements.
About these practice questions
One of 144 original CTFL-v4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.