1. Software testing definition 2. Testing definition 3. Test cases 4. Types of Software testing

1. BABASAHEB BHIMRAO AMBEDKAR UNIVERSITY
(UIET)
SEMINAR
TOPIC : SOFTWARE TESTING(UNIT-4)
PAPER OF TOPIC : SOFTWARE ENGINEERING(ECS-602)
PRESENTED BY
NAME: SURJEET KUMAR
COURSE : BTECH (CSE) – 6TH SEM.
ROLL NO. : 188726

2. AGENDA
 I N T R O D U C T I O N O F S O F T WA R E
 C O N C E P T S O F T E S T I N G
 N E E D O F T E S T I N G
 T Y P E S A N D T E C H N I Q U E S O F T E S T I N G
 C LO S I N G
2

3. 3
WHAT IS SOFTWARE ?
D E F I N I T I O N
Software comprises of the entire set of
programs, procedures , and routines associated
with the operation of a computer system.
3
The combination of programs, routines that
control the functioning of the hardware and
direct its operation.

4. 4
WHAT IS TESTING ?
 Testing is the technique to find out the failures or in the
source code .
 It is the evaluation of the software against requirements
gathered from users and system specification.
 Some terminologies used are-
4
• Errors
• Failures
• Test case
• Test suits

5. 5
. 5
 Testing consumes the largest effort among all
development activities.
 Largest manpower among all roles.
 Testing is getting more complex day by day
due to –
CONCEPTS OF TESTING
• Larger and more complex programs
• Newer programming paradigms.
• Newer testing techniques.
• Test automation.

6. BEFORE MOVING
FORWARD
6
TEST CASES
 It describes the state of software.
 Test case is a triplet [I, S, O]
 I is the input data to system .
 S is the state of the system.
 O is the expected output of the
system.

7. WHY WE NEED
TESTING ?
L E T ’ S D I V E I N
7

8. .
 It discovers errors and bugs .
 Makes the software more reliable and easy to use.
 Decreases the cost of maintenance.
 Writing testable codes improves overall quality.
NEED OF TESTING

9. WHAT’S NEXT?
L O O K I N G A H E A D
9
STRATEGIES AND
TECHNIQUES

10. 4 TESTING LEVELS
10
Unit testing
• Test each module independently
• Mostly done by developers of the module
Integration testing
• Test the system as a whole
• Done by separate testing or quality assessment(QA) team
System testing
• Test the all module together.
• Done by separate testing or QA team.
Acceptance and regression testing
• Validation of the system functions by the customer

11. TYPES OF SYSTEM
TESTING
. 11
Based on type of test
• Functionality test
• Performance test
Based on who perform testing
• Alpha test
• Beta test
• Acceptance test

12. TESTING TECHNIQUES
WHITE BOX
TESTING
 Focus on the code structure
of the program.
 Also known as glass box or
clear box testing.
BLACK BOX
TESTING
 Focus on the functional
specification of the
software.
 It is performed without
knowing the internal
structure of the software.
GREY BOX
TESTING
 Performed with the limited
information about internal
functionality of the system.
 It identifies context-specific
errors that belong to web
systems.
12

13. WHITE BOX TESTING
13
WHITE BOX
TESTING
COVERAGE BASED FAULT BASED
 Statement coverage
 Branch coverage
 Path coverage
 Condition coverage
 MC/DC coverage
 Data flow-based testing
 Mutation testing

14. BLACK BOX TESTING
14
 The goal is to achieve thoroughness of
exhaustive input testing.
 It can be applied to each and every
level of the software testing such as
Unit, Integration, System and
Acceptance testing.
 There are many strategies
• Scenario coverage
• Equivalence class partitioning
• Boundary value testing
• Cause-effect testing
• Combinatorial testing

15. GREY BOX TESTING
15
 It provides the combined benefits
of both white-box and black-box.
 Based on the functional
specification, UML diagrams, or
database diagrams.
 Grey-box testing techniques
involves :
• Regression testing.
• Patterns testing
• Orthogonal array testing
• Matrix testing

16. 16
SUMMARY
TESTING PLAYS IMPO RTA NT RO LE
Errors and bugs are detected and removed.
TESTING CO NS UMES THE MA X TIME
Almost 80% time is taken by testing phase.
TEST CA S ES A R E CR UCIA L PA RT
Test cases must be according to the client`s expectation.
R IGHT STR ATEGY S HO ULD BE CHO S E N
Without right strategy it is difficult to make software error free
16

17. THANK YOU
.