Scribd
Upload
566 views

Presented By: Deepika Amrit Pooja Prabhjot

Software Testing a presentation on software testing prepared for class presentations It¶s a process of validating and verifying that a software program/product: meets the requirements. works as expected Can be implemented with the same characteristics raising the quality and reliability of the program Need of testing y Quality y Rework and re-testing y Method of finding bugs Types of software Testing y Unit testing y Integration testing Unit testing y Testing of individual software components or modules y

Uploaded by

poojuuu
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
566 views

Presented By: Deepika Amrit Pooja Prabhjot

Software Testing a presentation on software testing prepared for class presentations It¶s a process of validating and verifying that a software program/product: meets the requirements. works as expected Can be implemented with the same characteristics raising the quality and reliability of the program Need of testing y Quality y Rework and re-testing y Method of finding bugs Types of software Testing y Unit testing y Integration testing Unit testing y Testing of individual software components or modules y

Uploaded by

poojuuu
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 27

Presented by:

Deepika
Amrit
Pooja
Prabhjot
Software Testing
 It’s a process of validating and verifying
that a software program/product:
◦ meets the requirements.
◦ works as expected
◦ Can be implemented with the same
characteristics
◦ raising the quality and reliability of the
program
Need of testing
Quality
Rework and re-testing
Method of finding bugs
Types of software Testing
Unit testing
Integration testing
Unit testing
Testing of individual software
components or modules
Done by the programmer
Requires detailed knowledge of
the internal program design and
code.
Unit testing frameworks
Goal
Take the smallest
piece of testable
software
Determine
whether it
behaves exactly
as expected
How UT fits into SDLC???

Unit Testing Tasks


Unit Testing Tasks
Create a Test Plan
Create Test Cases and Test Data
If applicable create scripts to run test
cases
Once the code is ready execute the
test cases
Fix the bugs if any and re test the code
Repeat the test cycle until the “unit” is
free of all bugs
Steps to Effective Unit Testing
Documentation
What should be done
Automate where necessary
Integration testing
Definition
 Modules
– Code Modules
– Individual Applications
– Client and server applications on a
network, etc.
 Relevant to:
– Client/server systems
– Distributed systems.
 Example
–Yahoo Mail
Various Types of Integration
Testing
Top-down approach
Bottom-up approach
Bottom Up approach
Definition
Use Of Test Drivers

Hierarchy Of Bottom Up
Steps to be followed
Combination Of Lower
Level Components
A S/W Driver
A Cluster Is Tested
Removal Of Drivers
Top Down Integration Testing
Definition
Use Of Stubs
Replacement Of Stubs
Depth First Manner
Breadth First Manner
Steps
◦ Test Drivers and Stubs
◦ Replacing Stubs
◦ Test
◦ Continue with nest
component
Methods of testing

white-box black-box
methods methods

Methods

Strategies
White box testing
It is a test case
design method
Uses the control
structure
Method used in

◦ Unit testing
◦ Integration testing
◦ Regression testing
Need of white box testing
To discover following types of bugs
◦ Logical errors
◦ Design errors
◦ Syntax errors
Ensureall independent paths are working
Examine all logical decisions
Examine all loops
Performing white box testing

Test each Test Test each


statemen each conditio
t decision n
Steps in white box testing
Test loops
Create
Test and
Profile internal
thetest
conditional
application plan
plans
subroutine
statements

inputs P
er
fo
r
m
se
Requirements
c
ur
Functional specifications
it
y
High level design documents
te
Detailed design documents
st
in
Source code
g
Limitation of WBT
Black Box Testing
What is black box ?
◦ Where behavior is determined just :

 By studying inputs
 By studying related outputs
What Is Black Box Testing?
Also called functional testing
Deals with :
◦ Inputs to system
◦ Outputs of system
Doesn’t deals with internal structure
Example Of Black Box Testing
Function To Draw A Triangle
It
accepts three numbers i.e. a, b, c
Three subdomains can be there :
◦ Scalene Triangle
◦ Isosceles Triangle
◦ Equilateral Triangle
Performing Black Box Testing
Lengths A B C

Scalene 3 4 5 VALID
5 4 3 VALID
4 5 3 VALID
 
Isosceles 5 5 8 VALID
5 8 5 VALID
8 5 5 etc. VALID
 
Equilateral 5 5 5 VALID
 
Bad Inputs -1 2 4 INVALID
3 -2 -5 INVALID
0 0 0 INVALID
Features Of Black Box Testing
Doesn’t require programming knowledge
Tester and programmer independent of
each other
Effective on Larger units
Conclusion

Thanks

You might also like