📖 ISTQB & Testing Core

ISTQB & Testing Core: ISTQB is an accreditation framework for software testing similar to the certification system in medicine — just as an anesthesiologist's dosage protocol is

ISTQB is an accreditation framework for software testing similar to the certification system in medicine — just as an anesthesiologist's dosage protocol is the same worldwide, ISTQB's 7 Principles ensure teams in different countries speak the same conceptual language. But if Java already gives you JUnit and TestNG, why do you need a separate ISTQB framework on top? Because JUnit is a vocabulary of tools; ISTQB answers when, why, and based on which risk analysis you use those tools. The most critical QA context: in interviews and multinational projects, debates like 'should we run regression or smoke tests?' cannot find common ground without ISTQB terminology — they stay silent disagreements that pave the way for defective production releases.

The 7 Principles of Software Testing

These 7 principles defined by ISTQB should guide every test engineer's mindset:

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

5. Beware of the pesticide paradox

6. Testing is context dependent

7. Absence-of-errors fallacy

Static Testing vs Dynamic Testing

Levels of Software Testing

Test Types: Functional vs Non-Functional

Tests are divided into two categories. Functional testing verifies *what* the system does (e.g. login, payment). Non-functional testing evaluates *how well* the system performs (speed, security, stability under heavy load).