“Impart high quality knowledge & skills to students in the field of information technology, motivate research,

encourage industry consultancy projects & nurture human values and life skills”.

Software Testing

Session by

Dr. Aisha Fernandes

Associate Professor,Information
Technology Department
Goa Engineering College.

[email protected]
 Organization of this Lecture:

o Understanding Software testing

o Verification & Validation
o Software Quality Assurance
o Walkthroughs
o Inspections
o Attributes to be tested
o Levels of Testing
o Black box v/s White box testing
o Summary
o References

2 Lecture 10 Testing
 Learning Outcome

To be able to explain Software Quality assurance and

Software testing.

3 Lecture 10 Testing
What is Software testing ?

…. a method to check whether the actual software product matches

expected requirements and to ensure that software product is defect
free.

Why is Software testing important ?

…… if there are any bugs or errors in the software, it can be identified

early and can be solved before delivery of the software product.
Properly tested software product ensures reliability, security and high
performance which further results in time saving, cost effectiveness
and customer satisfaction.

Quotes on Testing
o “Testing is the process of executing a program with the intention of finding errors.”
– Myers
o “Testing can show the presence of bugs but never their absence.” - Dijkstra

Lecture 10 Testing 4
 Verification & Validation

Verification refers to the set of tasks that ensure that software correctly
implements a specific function.

Validation refers to a different set of tasks that ensure that the software that
has been built is traceable to customer requirements.

Boehm states :

Verification: “Are we building the product right?”

Validation: “Are we building the right product?”

Lecture 10 Testing 5
Software Quality Assurance
Software Quality Assurance (SQA) is a set of activities for
ensuring quality in software engineering processes.

-It works parallel to development of a software. Once

developers complete a phase, SQA team has to check for
correctness.
- The responsibilities of the SQA group include the
development of various standards to which the software must
conform as well as the establishment of the monitoring
procedures.

SQA team uses reviews.

Two types of reviews are popularly used:
1. Walkthroughs
2. Inspections

Lecture 10 Testing 6
 Walkthroughs
o Team of 4 to 6 individuals
(SQA representative, client representative, developer, manager
responsible, next phase representative)
Ø SQA group member should chair the walkthrough
Ø Members of walkthrough team should be experienced senior
members
Ø Material/Agenda of walkthrough should be distributed to team
members well in advance. Each reviewer must study the material and
prepare 2 lists; list of items the reviewer does not understand and list of
items the reviewer feels are incorrect.
Ø No walkthrough should last longer than 2 hours.

Ø The goal of walkthroughs is only to identify and record the faults

( not correct them !!)

Lecture 10 Testing 7
 Walkthroughs…continued

Two ways of conducting Walkthroughs:

ØParticipant Driven
( Participants present their 2 lists and the representative
answers the queries)

ØDocument Driven
( A person walks the participants through the document and
the participants interrupt with queries)

… A walkthrough is an interactive process !!

Lecture 10 Testing 8
 Inspections

o Proposed by Fagan for testing designs and code

o An inspection has 5 formal steps :

1. An overview of the document is given to all participants and at the end
,document is shared.
2. Participants try to understand the document in detail.
3. Inspection ( 1 participant walks through doc and fault finding begins)
4. Rework ( individual responsible resolves all faults)
5. Follow-up ( moderator ensures that all issues solved satisfactorily)

Lecture 10 Testing 9
 Attributes to be tested

o Reliability

o Robustness

o Performance

o Utility

o Correctness

Lecture 10 Testing 10
 Levels of Testing/ Testing Strategies

o Unit Testing (To test the unit of the program. It helps developers to know
whether the individual unit of the code is working properly or not.)

o Integration Testing (to see that the integrated units are working without
errors )

o System testing (software is compiled as a whole and then tested as a

whole. This testing strategy checks the functionality, security, portability,
etc)

o Validation Testing (Determine if the software meets all of the

requirements defined in the SRS)
n Regression Testing
n Alpha Testing
n Beta Testing

o Acceptance Testing

Lecture 10 Testing 11
 Black Box – White Box testing

Black Box Testing is a software testing method in which the internal

structure/ design/ implementation of the item being tested is not
known to the tester. Tester is only concerned with the inputs and
outputs.

White Box/Glass box Testing is a software testing method in which

the internal structure/ design/ implementation of the item being
tested is known to the tester. Tester has to make sure the logic/
processing is right.

Example : 2 + 2 is 4
2 * 2 is 4

Lecture 10 Testing 12
 Black Box v/s White Box testing

BLACK BOX TESTING WHITE BOX TESTING

It is a way of software testing in which It is a way of testing the software in
the internal structure or the program or which the tester has knowledge about
the code is hidden and nothing is known the internal structure or the code or the
about it. program of the software.
It is mostly done by software testers. It is mostly done by software developers.
No knowledge of implementation is Knowledge of implementation is
needed. required.
It can be referred as outer or external It is the inner or the internal software
software testing. testing.
It is functional test of the software. It is structural test of the software.
This testing can be initiated on the basis This type of testing of software is started
of requirement specifications document. after detail design document.
No knowledge of programming is It is mandatory to have knowledge of
required. programming.
It is the behavior testing of the software. It is the logic testing of the software.
It is applicable to the higher levels of It is generally applicable to the lower
testing of software. levels of software testing.
It is also called closed testing. It is also called as clear box testing.

https://www.geeksforgeeks.org/
Lecture 10 Testing 13
 Summary
ØSoftware Testing is a method to check whether the actual software
product matches the expected requirements.

ØVerification refers to the set of tasks that ensure that software

correctly implements a specific function.

ØValidation refers to a different set of tasks that ensure that the

software that has been built is traceable to customer requirements.

ØSoftware Quality Assurance (SQA) is a set of activities for ensuring

quality in software engineering processes.

ØIn Black box testing, Tester is only concerned with the inputs and
outputs.
ØIn White box testing, the tester is concerned with the working/ logic of
the function.

14 Lecture 10 Testing
 References :

1. Stephen Schach ,“Object Oriented and Classical

Software Engineering”, Tata Mc Graw Hill Publication.
2. https://www.guru99.com/software-testing-introduction-
importance.html

15 Lecture 10 Testing
 Any Questions…??

16 Lecture 10 Testing
17 Lecture 10 Testing