Customer satisfaction. Subjective term.It will depend on who is the “customer” is. Each type of customer will have their own view on “quality”

Measurement of how close is actual software product to the expected product

Does not make

reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable

The process of monitoring and improving all activities associated with software development, from requirements gathering, design and reviews to coding, testing and implementation.

Testing is mainly focused on the source code (black,gray and white box), Quality Assurance measures the quality of processes used to create a quality product

The purpose of testing is verification, validation and error detection

process is conformance and consistency by evaluating the results against pre-specified requirements.(Are we building the system right?)

process of what has been specified is what the user actually wanted. ( Are we building the right system? )

finding if things when they shouldn’t or things don’t happen when they should

testing is done without access to the source code

testing is done with access to the code. Bugs are reported at the source code level, not behavioural

testing is using structural, design and environmental information (complete or incomplete) to expand or focus black box testing and enhance testing productivity by using appropriate methods and tools

mismatch between actual behaviour of a software application and its expected behaviour.

mismatch between actual and expected look/usage of UI Design Element

from requirements, specifications, other technical documentation

is a format used by Business Analysts for specifying system requirements.

Clarying requirements. Bringing down percentage of code re-written due to the change in requirements

Testing aimed at showing software works as intended when user does correct actions

testing aimed at showing that software handles properly situations in which user acts not as user is supposed to act