Software testing is a process of executing a program or application with the intent of finding the software bugs. It can also be stated as the process of validating and verifying that a software program or application or product: Meets the business and technical requirements that guided it's design and development.

2. WHAT we’ll be EYING at?
• The BASICS : WHAT, WHY & WHO?
• Usual TERMINOLIGIES.
• VERIFICATION V/S VALIDATION.
• CATEGORIZING Testing.

3. ANSWERING : WHAT?
• Diverse Definition(s):-
TESTING is:-
– the process of demonstrating that errors are not
present.
– the process which shows that a program performs its
intended tasks correctly.
– The process for establishing confidence that a program
does what it is supposed to do.

4. DEFINING TESTING!
• Changing “THE INTENTION”:-
– Testing, assuming program has errors, rather than
testing whether it is working fine or not!
• Testing is the process of executing a program with
the intent of finding errors.
– Has a psychological effect associated with it i.e.
Human Beings are GOAL ORIENTED.(Aren't we all?)

5. ANSWERING : WHO? &
WHAT to TEST?
• Difficult for a programmer to point out errors
from own creations.
• Different people for respective tasks.
• Should always test vulnerable areas(error prone)
since complete testing can be exhaustive.

6. ANSWERING : WHY?
• TESTED S/W expenses < NOT TESTED S/W expenses
– In many cases the potential loss can be enormous!
– Imagine untested medical instruments(will u use?), an
untested Car(will u drive?)…(involves Human Safety)
• Precaution is always better than cure.

7. TERMINOLIGIES
• ERRORS : What we know as MISTAKES. Involves
Human Interaction.
• FAULT : Errors leads to Fault. It is a representation of
an error(immediate after effect). Defect is a good
synonym.

8. TERMINOLIGIES
• FAILURE : When a fault executes we get a failure.
Failure is dynamic.

9. VERIFICATION V/S VALIDATION
VERIFICATION
• Are we building the system
right?
• It is the process of evaluating
products of a development
phase to find out whether
they meet the specified
requirements.
• Activities involved : Reviews,
Meetings & Inspections.
• Cost of errors caught is less
than cost of errors found
during Validation.
VALIDATION
• Are we building the right
system?
• It is the process of evaluating
software at the end of the
development phase to check
whether the software satisfies
customer’s requirements.
• Activities involved : Black Box
Testing & White Box Testing.
• Cost of errors caught is more
than cost of errors found
during Verification.

10. TESTING: DIGGING DEEP!
• On the basis of End Users Testing can be broadly
classified as:-
• If Specific Customer then Acceptance Testing.
– Done by End User/Customer.
– May vary from ad-hoc tests to well planned ones.
• If Anonymous Customer then Alpha & Beta Testing.
– Alpha Tests are conducted at developer’s site under
controlled environment.
– Beta Tests are conducted by End Users/Customers at
their sites in a real environment.

11. TESTING : A BIRD’s EYE VIEW
FUNCTIONAL TESTING
• Tester tests how well the
system performs.
• Based on Client’s
Requirements.
• Unit Testing, Integration
Testing, Smoke Testing, Sanity
Testing, Regression Testing are
some examples.
• a.k.a. BLACK BOX TESTING .
NON FUNCTIONAL TESTING
• Tester tests how well the
system responds.
• Based on Client’s
Expectations.
• Load/Performance Testing,
Stress/Volume Testing,
Security Testing, Installation
Testing are few examples.
• a.k.a. WHITE BOX TESTING.