Scribd
Upload
4 views4 pages

ISTQB Foundation Level Short Note1

The ISTQB Foundation Level document outlines the fundamentals of software testing, emphasizing the importance of identifying defects and ensuring software reliability through various testing principles and methodologies. It covers testing throughout the software development lifecycle, including different development models, test levels, types, and design techniques, as well as static testing and test management practices. Additionally, it provides guidance on tool support for testing and exam preparation tips for candidates.

Uploaded by

kavindyalearnings
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views4 pages

ISTQB Foundation Level Short Note1

The ISTQB Foundation Level document outlines the fundamentals of software testing, emphasizing the importance of identifying defects and ensuring software reliability through various testing principles and methodologies. It covers testing throughout the software development lifecycle, including different development models, test levels, types, and design techniques, as well as static testing and test management practices. Additionally, it provides guidance on tool support for testing and exam preparation tips for candidates.

Uploaded by

kavindyalearnings
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

ISTQB Foundation Level Short Note (Concise)

1. Fundamentals of Testing

• What is Testing?

o Evaluating software to identify defects and ensure it meets requirements.

o Verification (building the product right) vs. Validation (building the right
product).

• Why is Testing Necessary?

o Prevent costly defects, ensure reliability, and reduce risk.

• Seven Testing Principles:

1. Testing shows the presence of defects, not their absence.

2. Exhaustive testing is impossible.

3. Early testing saves time and money.

4. Defects cluster together (80/20 rule).

5. Beware of the pesticide paradox (repeated tests lose effectiveness).

6. Testing is context-dependent.

7. Absence of errors is a fallacy (error-free does not mean user satisfaction).

2. Testing Throughout the Software Development Lifecycle

• Development Models:

o Waterfall: Linear, phase-based.

o V-Model: Each development phase has a corresponding testing phase.

o Agile: Iterative, testing in every sprint.

o Iterative and Incremental: Repeated cycles of development and testing.

o Spiral: Combines iterative development with risk assessment.

• Test Levels:

o Unit Testing: Individual components.

o Integration Testing: Interaction between components.


o System Testing: Full, integrated system.

o Acceptance Testing: Validating against user requirements.

• Test Types:

o Functional: Validates functional requirements.

o Non-Functional: Performance, security, usability.

o Structural: White-box testing of code structure.

o Change-Related: Regression and re-testing.

• Test Maintenance:

o Continuous updates as software evolves.

3. Static Testing

• Techniques:

o Reviews: Formal/informal evaluation of documents or code.

o Walkthroughs: Step-by-step presentation.

o Inspections: Formal, with defined roles and checklists.

• Benefits:

o Early defect detection, reduced cost, better quality.

4. Test Design Techniques

• Black-Box:

o Equivalence Partitioning: Valid/invalid input groups.

o Boundary Value Analysis: Focus on edge cases.

o Decision Tables: Complex business rules.

o State Transition Testing: Different system states.

• White-Box:

o Control Flow: All possible paths.

o Data Flow: Data usage and variable states.

o Statement Coverage: Every line executed.


o Decision Coverage: All decision points.

• Experience-Based:

o Error Guessing: Based on tester experience.

o Exploratory Testing: Learning, test design, execution.

o Checklist-Based Testing: Predefined checklists.

5. Test Management

• Test Planning and Estimation:

o Scope, resources, timelines.

• Monitoring and Control:

o Track progress, adjust plans.

• Configuration Management:

o Manage test artifacts and versions.

• Risk-Based Testing:

o Prioritize based on risk.

• Defect Lifecycle:

o New -> Assigned -> Fixed -> Retested -> Closed.

6. Tool Support for Testing

• Types of Tools:

o Test management, test execution, defect tracking, CI/CD, performance,


automation.

• Tool Selection:

o Based on project needs, budget, and skills.

7. Exam Tips

• Understand concepts, not just memorize.


• Practice sample questions.

• Review past projects and real-world scenarios.

• Use the ISTQB glossary and terminology.

You might also like