Testing PPT Vinay21csu380

SOFTWARE
TESTING
PRESENTED
BY VINAY 21CSU380
INTRODUCTION
 It is the process used to identify the correctness,

completeness and quality of developed computer
software.
 It is the process of executing a program or application

under positive and negative conditions by manual or
automate means. It checks for the:-
 Specification
 Functionality
 Performance
OBJECTIVES
 Uncover as many as errors (or bugs) as possible in a
given product.
 Demonstrate a given software product matching its

requirement specifications.
 Validate the quality of a software testing using the

minimum cost and efforts.
 Generate high quality test cases, perform effective tests,

and issue correct and helpful problem reports.
ERROR, BUG, FAULT & FAILURE
 Error: It is a human action that produces the
incorrect result that produces a fault.
 Bug: The presence of error at the time of

execution of the software.
 Fault: State of software caused by an error.
 Failure: Deviation of the software from its

expected result. It is an event.
SDLC(Software Development Life
Cycle)
 Standard model used word wide to develop a software.
 A framework that describes the activities performed at

each stage of a software development project.
 Necessary to ensure the quality of the software.
 Logical steps taken to develop a software product.

CLASSICAL WATERFALL MODEL
TESTING LIFE CYCLE
TEST PLAN
 It is a systematic approach to test a system i.e.
software. The plan typically contains a
detained understanding of what the eventual
testing workflow will be.
TEST CASE
 It is a specific procedure of testing a particular
requirement.
 It will include:
 Identification of specific requirement tested
 Test case success/failure criteria
 Test case steps to execute test
 Test data
VERIFICATION vs VALIDATION
 VERIFICATION: The software should
confirm to its specification ( Are we building
the product right? )
 VALIDATION: The software should do what

the user really requires ( Are we building the
right product? )
TESTING METHODOLOGIES
Black box testing
White box testing

BLACK BOX TESTING AND WHITE
BOX TESTING
 Black box testing:-
No knowledge of internal program or code required.

Tests are based on requirements and functionality.
White box testing:-
Knowledge of internal program and code required

Tests are based on coverage of code statements,
branches, paths and conditions.
BLACK BOX TESTING
WHITE BOX TESTING
TESTING LEVELS
 Unit testing
 Integration testing
 System testing
UNIT TESTING
 Tests each module individually
 Follows a white box testing
 Done by developers
INTEGRATION TESTING
 Once all the modules have been unit tested,
integration testing is performed.
 • It is systematic testing." Produce tests to
identify errors associated with interfacing.
 Types:
 Big Bang Integration testing
 Top Down Integration testing
 Bottom Up Integration testing
 Mixed Integration testing
SYSTEM TESTING
 The system as a whole is tested to uncover requirement
error.
 Verifies that all system elements work properly and that

overall system function and performance has been achieved.
 Types:
 Alpha Testing
 Beta Testing
 Acceptance Testing
 Performance Testing
TESTINGS
 ALPHA TESTING
 It is carried out by the test team within the developing organization.
 BETA TESTING
 It is performed by a selected group of friendly customers.
 ACCEPTANCE TESTING
 It is performed by the customer to determine whether to accept or
reject the delivery of the system.
 PERFORMANCE TESTING
 It is carried out to check whether the system meets the
nonfunctional requirements identified in the SRS document.
TYPES OF PERFORMANCE TESTING
 Stress Testing
 Volume Testing
 Configuration Testing
 Compatibility Testing
 Regression Testing
 Recovery Testing
 Maintenance Testing
 Documentation Testing
 Usability Testing
DISCUSSION
 In order to be cost effective, the testing must be
concentrated on areas where it will be most effective.
 The testing should be planned such that when testing is

stopped for whatever reason, the most effective testing in
the time allotted has already been done.
 The absence of an organizational testing policy may

result in too much effort and money will be spent on
testing, attempting to achieve a level of quality that is
impossible or unnecessary.

Testing PPT Vinay21csu380

Uploaded by

Copyright:

Available Formats

Testing PPT Vinay21csu380

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Testing PPT Vinay21csu380

Uploaded by

Copyright:

Available Formats

SOFTWARE

 It is the process used to identify the correctness,

 It is the process of executing a program or application

 Demonstrate a given software product matching its

 Validate the quality of a software testing using the

 Generate high quality test cases, perform effective tests,

 Bug: The presence of error at the time of

 Fault: State of software caused by an error.

 Failure: Deviation of the software from its

 A framework that describes the activities performed at

 Necessary to ensure the quality of the software.

 Logical steps taken to develop a software product.

 VALIDATION: The software should do what

Black box testing

White box testing

No knowledge of internal program or code required.

White box testing:-

Knowledge of internal program and code required

 Follows a white box testing

 Verifies that all system elements work properly and that

 The testing should be planned such that when testing is

 The absence of an organizational testing policy may

You might also like