iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Modern quality assurance (QA) is not a final inspection or another name for manual testing. It is the connected work of building confidence that software meets its requirements and performs acceptably for people using it in a particular context. Tests provide evidence about code; QA helps teams decide what evidence they need, how to gather it, and what it means for the product in reality.
What QA does in software development
QA connects product intent to evidence. Teams clarify what the software is supposed to do, examine requirements and other work products, evaluate the software at appropriate levels, and use results to guide decisions. That work can occur throughout a lifecycle; it is not confined to a release-day gate or assigned automatically to one dedicated QA department.
The ISTQB Foundation Level syllabus covers testing knowledge relevant to Waterfall, Agile, DevOps, and Continuous Delivery. It includes fundamentals, lifecycle testing, test levels and types, static testing, analysis and design, test management, defect management, and tool support. This is a map of relevant knowledge, not a claim that every organization allocates each responsibility to a QA team. ISTQB Foundation Level overview
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQA, quality control, and testing are related—but different
- Quality assurance is the broader concern of building confidence in quality, including attention to the processes used to create and evaluate software.
- Quality control evaluates outputs against expectations. Testing is a major quality-control activity.
- Testing comprises activities to discover and evaluate properties of a test item. It includes planning, preparation, execution, reporting, and management—not just running checks.
- Verification and validation describe related quality purposes. Testing can provide evidence for them, but cannot guarantee that software is fit for every real-world use.
ISO/IEC/IEEE 29119 describes testing concepts and processes intended for different organizations and lifecycle models. The series covers organizational and management processes, dynamic testing, documentation, and test-design techniques. Its concepts identify risk-based testing as the recommended approach for focusing effort. ISO/IEC/IEEE 29119-1:2022 · ISO/IEC/IEEE 29119-2:2021 · ISO/IEC/IEEE 29119 series overview
What testing can—and cannot—establish
Testing can reveal defects and supply evidence about a product under the conditions examined. It cannot prove that defects are absent: software has too many possible inputs, states, environments, and interactions for exhaustive testing to be practical. Teams therefore sample and prioritize, choosing tests that address the most relevant risks and quality goals.
“Testing shows the presence, not the absence of defects.” — ISTQB, Certified Tester Foundation Level Syllabus v4.0.1, section 1.3, dated September 15, 2024. ISTQB Foundation Level syllabus
This is the code-versus-reality gap: a passing test suite says that the tested behavior met the checks under their conditions. It does not by itself establish that users will find the product usable, secure, dependable, or suitable in every context. Those conclusions require evidence matched to the intended users, operating conditions, and possible harms.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →How teams choose a testing strategy
A useful strategy selects test levels and types according to risk, product goals, and context. These categories answer different questions and can be combined; they are not mutually exclusive stages or a universal allocation formula.
Choose the scope: test levels
- Component testing examines an individual component and its behavior.
- Integration testing looks at interactions between components or systems.
- System testing evaluates the system as a whole against relevant requirements.
- Acceptance testing gathers evidence about whether the system is acceptable for its intended use or stakeholders.
Choose the question: test types
- Functional testing asks whether specified functions behave as expected.
- Usability testing examines how people interact with the product.
- Security testing investigates security-related risks and behavior.
- Performance testing evaluates performance characteristics under relevant conditions.
A type can be applied at more than one level. For example, teams can examine security at a component boundary, between integrated services, or across a complete system. The right choice depends on where a failure could occur and which consequences matter.
Choose when to look: static and dynamic approaches
Static testing evaluates work products without executing the software; reviews can find issues in requirements, designs, or code before a running system is available. Dynamic testing evaluates software by running it. Both can contribute evidence, and they serve different purposes.
Rank #4
Prioritize by risk and context
Risk-based testing directs effort toward the failures most relevant to the product and its stakeholders. Teams can ask what might fail, who could be affected, under what conditions, and how serious the outcome would be. Context matters: the same feature may have different quality expectations depending on who uses it and how.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →There is no single test-level ratio or fixed testing pyramid established as a requirement for every product. The standards support choosing levels and types in relation to strategy and risk, rather than prescribing one allocation for all teams. ISO/IEC/IEEE 29119-1:2022 concepts
Best Value
Product quality is not the same as quality-in-use
“Quality” is multidimensional. Product quality concerns properties of the software or ICT product. Quality-in-use concerns outcomes and characteristics that depend on stakeholders using a system in a specified context. A product can satisfy a technical property while still falling short for the people using it under actual conditions.
ISO/IEC 25010:2023 defines a product quality model with nine characteristics as a reference for specifying, measuring, and evaluating product quality. ISO/IEC 25019:2023 defines a quality-in-use model for a specified context. ISO/IEC 25020:2019 provides a framework for constructing and selecting quality measures; ISO confirmed it as current in 2025.
| Reference | Focus | How it helps |
|---|---|---|
| ISO/IEC 25010:2023 | Product quality | Reference model for specifying, measuring, and evaluating product properties |
| ISO/IEC 25019:2023 | Quality-in-use | Frames quality in a specified context involving stakeholders using a system |
| ISO/IEC 25020:2019 | Quality measurement | Framework for constructing and selecting measures; confirmed current in 2025 |
Measures should follow the product’s goals and context. Counts such as tests written or defects found can describe activity, but alone they do not demonstrate good outcomes for users. A meaningful quality assessment connects measurements to the properties and contexts the team intends to evaluate.
What this means for a QA team
Modern QA is best understood as a portfolio of responsibilities shared across the product lifecycle and, depending on the organization, across roles. Its purpose is not to promise perfect software. It is to make quality expectations explicit, gather relevant evidence, communicate uncertainty and risk, and help stakeholders make informed decisions about whether the product is ready for its intended use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
