Cheat sheet
ISTQB Foundation Cheat Sheet
Testing Fundamentals
- 20% of exam
- Core Terms Seven Principles Test Process Testing Mindset
Testing Across SDLC
- 15% of exam
- SDLC Models Test Levels Test Types Maintenance Testing
Static Testing
- 10% of exam
- Static Basics Review Roles Review Types Review Picker
Test Analysis + Design
- 28% of exam
- Black-Box White-Box Experience-Based Technique Picker
Managing Test Activities
- 23% of exam
- Risk-Based Testing Metrics Defects Report Picker
Test Tools
- 5% of exam
- Tool Types Automation Tool Risks Tool Picker
Quick Facts
- Exam CTFL v4.0
- Questions 40 MCQ
- Points 40 total
- Pass 26/40
- Time 60 min
- Extension 75 min
- Prereq None
- Focus Apply concepts
Defect Chain FU
- Error -> Defect -> Failure
- Human error Work product defect Runtime failure Root cause why
Verification vs Validation FU
Verification
- Meets specification
- Built right
- Requirements focus
Validation
- Meets need
- Right product
- User focus
- Spec vs need
Process Picker FU
- Define scope → Planning
- Track progress → Monitoring
- Change approach → Control
- Find conditions → Analysis
- Write cases → Design
- Prepare suites → Implementation
- Run tests → Execution
- Archive evidence → Completion
Core Terms FU
- Error Human mistake
- Defect Work product flaw
- Failure Observed wrong behavior
- Root cause Underlying reason
- Quality Needs satisfied
- Risk Likelihood x impact
- Testware Testing work products
- Traceability Linked test evidence
Process Flow FU
- Plan, analyze, design, build, run, close
- Planning Analysis/design Implementation/execution Completion
Testing vs Debugging FU
Testing
- Reveal failures
- Provide evidence
- Report defects
Debugging
- Find cause
- Fix defect
- Confirm fix
- Find vs fix
Seven Principles FU
- Presence Shows defects
- Exhaustive Normally impossible
- Early Find defects sooner
- Clustering Defects group
- Pesticide Tests go stale
- Context Approach varies
- Fallacy Wrong product fails
Test Process FU
- Planning Objectives and approach
- Monitoring Compare actual plan
- Control Adjust testing
- Analysis Identify test conditions
- Design Create test cases
- Implementation Prepare testware
- Execution Run and log
- Completion Close and archive
Test Levels SD
- Component -> Integration -> System -> Acceptance
- Unit first Interfaces next Whole system Business fit
Confirmation vs Regression SD
Confirmation
- Retest fix
- Same failure
- Defect closed
Regression
- Check side effects
- Existing behavior
- Change impact
- Fix vs side effects
SDLC Models SD
- Sequential Phased delivery
- V-model Test levels aligned
- Iterative Repeated cycles
- Incremental Partial delivery
- Agile Short feedback loops
- DevOps Build-operate feedback
- Shift-left Test earlier
- Retrospective Improve process
Test Levels SD
- Component Single unit
- Integration Interfaces interact
- System Whole system
- Acceptance Fit for use
- Driver Calls component
- Stub Simulates called part
- Contract Interface expectation
- Environment Execution context
Test Types SD
- Functional What it does
- Non-functional How it behaves
- White-box Internal structure
- Change-related After modification
- Confirmation Fix works
- Regression Nothing broke
- Maintenance Changed live system
- Impact analysis Change consequences
Static vs Dynamic ST
Static
- No execution
- Find early
- Reviews/tools
Dynamic
- Execute software
- Observe failures
- Runtime evidence
- Inspect vs run
Review Picker ST
- Quick feedback → Informal
- Author explains → Walkthrough
- Expert consensus → Technical review
- Formal defects → Inspection
- Tool scans code → Static analysis
- Viewpoint assigned → Perspective reading
Static Basics ST
- Static testing No execution
- Dynamic testing Execute software
- Review Human examination
- Static analysis Tool examination
- Checklist Prompt defects
- Scenario reading Workflow viewpoint
- Role-based Stakeholder viewpoint
- Perspective-based Assigned viewpoint
Review Roles ST
- Author Created work product
- Moderator Runs review
- Facilitator Guides meeting
- Scribe Records findings
- Reviewer Finds anomalies
- Manager Provides resources
- Leader Owns review
- Participants Review team
Review Types ST
- Informal Ad hoc feedback
- Walkthrough Author-led review
- Technical review Consensus defects
- Inspection Formal review
- Planning Define scope
- Kick-off Align reviewers
- Individual review Find issues
- Communication Discuss findings
Coverage Strength TE
- Decision coverage includes statement coverage
- Branches imply lines Lines miss branches K3 calculation
EP vs BVA TE
EP
- Value classes
- One representative
- Valid/invalid
BVA
- Class edges
- Boundary neighbors
- Range defects
- Class vs edge
Technique Picker TE
- Input classes → EP
- Range edges → BVA
- Business rules → Decision table
- States change → State transition
- Code paths → White-box
- Weak specs → Exploratory
Black-Box TE
- EP Partition values
- BVA Test edges
- Decision table Condition combinations
- State transition States and events
- Use case User workflow
- Coverage Items exercised
- Valid class Accepted values
- Invalid class Rejected values
Statement vs Decision TE
Statement
- Lines executed
- Weaker coverage
- Misses branches
Decision
- Outcomes executed
- Stronger coverage
- Covers branches
- Line vs branch
White-Box TE
- Statement Executable statement
- Statement coverage Statements executed
- Decision Branch outcome
- Decision coverage Outcomes executed
- Cyclomatic Independent paths
- Control flow Execution paths
- Data flow Variable lifecycle
- Dead code Unreachable code
Experience-Based TE
- Error guessing Likely mistakes
- Exploratory Learn while testing
- Checklist-based Guided experience
- Charter Exploration mission
- Session Timeboxed testing
- Heuristic Helpful rule
- Attack Targeted fault idea
- Tour Exploration pattern
Risk Formula MA
- Risk = likelihood x impact
- Likelihood Impact Priority Residual risk
Severity vs Priority MA
Severity
- Technical impact
- Failure seriousness
- Quality view
Priority
- Business urgency
- Fix order
- Stakeholder view
- Impact vs urgency
Management Basics MA
- Test plan Scope and approach
- Entry criteria Start conditions
- Exit criteria Stop conditions
- Estimation Predict effort
- Prioritization Order by value
- Strategy Overall test approach
- Independence Less bias
- Whole team Shared quality
Product vs Project Risk MA
Product
- Quality failure
- User impact
- System behavior
Project
- Delivery threat
- Schedule/cost
- Team constraints
- Quality vs delivery
Risk Management MA
- Product risk Quality threat
- Project risk Delivery threat
- Likelihood Chance of failure
- Impact Damage if occurs
- Risk level Likelihood plus impact
- Mitigation Risk reduction
- Residual risk Remaining exposure
- Risk control Ongoing response
Metrics + Reports MA
- Progress Run/not run
- Quality Product measures
- Defect metrics Found/fixed counts
- Coverage Requirements or code
- Cost metrics Testing spend
- Progress report Ongoing status
- Completion report Final summary
- Dashboard Visual status
Defects + Config MA
- Anomaly Possible problem
- Defect report Failure record
- Severity Technical impact
- Priority Business urgency
- Lifecycle Defect states
- CM Version integrity
- Baseline Approved version
- Change control Managed updates
Tool Picker TO
- Trace requirements → Management tool
- Scan source → Static tool
- Run regression → Execution tool
- Measure branches → Coverage tool
- Simulate load → Performance tool
- Pipeline feedback → CI tool
Tool Types TO
- Management tool Plan and track
- Static tool Analyze work products
- Design tool Generate tests
- Execution tool Run tests
- Coverage tool Measure exercised code
- Performance tool Simulate load
- Monitoring tool Observe operation
- CI tool Pipeline feedback
Automation TO
- Benefit Fast repeatability
- Risk False confidence
- Maintenance Script upkeep
- Pilot Small evaluation
- Rollout Phased adoption
- ROI Value over cost
- Data-driven Inputs separated
- Keyword-driven Action words
Common Traps
Testing proof
- Shows defects ≠ Never proves absence
Testing scope
- Includes work products ≠ Not execution only
Validation wording
- User need ≠ Not just specification
Debugging owner
- Fixing cause ≠ Not reporting failure
BVA targets
- Edges matter ≠ Middle optional
Decision tables
- Combinations tested ≠ Not single ranges
Acceptance testing
- Confidence for use ≠ Not unit checks
Automation promise
- Supports testing ≠ Never replaces judgment
Severity priority
- Severity is impact ≠ Priority is urgency
Risk-based testing
- Prioritizes effort ≠ Does not remove risk
Last Minute
- 1. CTFL: 40Q, pass 26
- 2. K3 means apply
- 3. Ch4 has most questions
- 4. Error causes defect
- 5. Failure is observed
- 6. Testing is evidence
- 7. Verification checks specification
- 8. Validation checks need
- 9. Static means no execution
- 10. EP classes, BVA edges
- 11. Decision table for combinations
- 12. Regression checks side effects
- 13. Severity impact; priority urgency
- 14. Risk equals likelihood impact
- 15. Automation needs maintenance
ISTQB Foundation Level (CTFL)
- Practice Questions 200 questions Study Guide 36 topics Cheat Sheet 143 facts Flashcards 50 cards Videos 1 video Blogs 1 blog Free CE Podcast