System testing

By Krishan Kumar
 Different Phases Of SDLC

Phase 1
• Planning

Phase 2
• System analysis and requirement

Phase 3
• Systems Design

Phase 4
• Development

Phase 5
• Integration and testing

Phase 6
• Implementation

Phase 7
• Operation And maintainence
 Types Of
Testing

Software
testing types

Basic of Level of Categories of

software software software
testing Testing testing
 Basics of software Testing Level of Software Testing Categories Of software Testing
• Black Box Testing • Unit Testing • GUI
• White box Testing • Integration Testing • Functional
• Grey Box Testing • System Testing • Validation
• User Acceptance Testing • Security
• Smoke and Sanity
• Regression
• Monkey
• Gorrila
• Agile
• Usability
• Exploratory
• Adhoc
• Static and dynamic
• Compatability
• Strees/Load testing
• Poerformance
• Volume testing
 Basic Of
Software
Testing

Black White Grey

Box Box Box
Testing Testing Testing
 Difference Between Black Box, White box
and Grey Box Testing
Black Box
• Tester has no information of the
inner workings of the IT Product
under test.
• Black box testing techniques can be
performed by developers, user
groups and testers.
White Box Testing
• Testers have full knowledge of inner • Both black box testing and white
programming rationale of the IT
product under test.
• Execution of automated white box
testing is the selective domain of the
testing and improvement group.
Gray Box testing
box testing are utilized(Mainly for
database testing).
• In gray box testing techniques inner
programming is partially known.
• Somewhat knowledge of internal
working of application is known.
• Performed by end clients and
furthermore by testers and
developers.
 Performance

Security Strees

System
Reliability Testing Scalability

Interoperability Localization
 Performance Testing
• Every system will have implicit
performance requirements. The
software should not take infinite
time or infinite resource to execute.
• “Performance Bugs” sometimes are
used to refer to those design
problems in software that cause the
system performance to degrade
Stress Testing
• This is done to find out if the
product’s behavior degrades under
extreme conditions and when it is
denied the necessary resources.
• It is expected to gracefully degrade
on increasing the load but the
system is not expected to crash at
any point of time during stress
testing.
• This helps to understand how the
system behaves under extreme and
realistic situations.
 Scalability Testing
• Scalability testing is also
called as Load Testing.
• This testing requires
enormous amount of
resource to find out the
maximum capability of
the system parameters.
Localization testing
• It is about global
functioning of the
product. It will verify that
the application still
works, even after it has
been translated into new
language or adopted for
a new culture.
 Interoperability Testing Reliability Testing
• IT ensures that two or • To verify the ability of the
more products can subsystem of a system to
exchange information, use confirm that it performs
the information, and work the user required functions
closely. without any frequent
errors.
• It is to check that how long
and how efficiently system
work without any error.
 Security Testing
• Software quality, reliability and security are
tightly coupled. Flaws in software can be
exploited by intruders to pen security holes.
With the development of the Internet, software
security problems are becoming even more
severe.
• Simulated security attacks can be performed to
find vulnerabilities.
Objectives
• Uncover as amny as errors (or bug) 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 effictive tests, and issue
correct and helpful problems reports.
• To find and correct defects.
• To check whether the client/user needs are satisfied.
• To avoid user detecting problems
• Also to provide Quality product.
IPO Chart
• IPO chart describes each functional
module of hierarchy chart by listing
inputs, processing steps, and outputs.
• IPO charts do not show hierarchy. It is
normally prepared for each function
shown on the hierarchy chart.
 IPO Chart
IPO Chart for costumer billing system hierarchy chart

Input Process Output

• Sale data • Verify account • Transaction

• Payment data number file
• New accounts • Validate all • Error report
• Inactive numeric fields
accounts • Check for
valid
transcation
codes.

IPO Charts are used for Input – Output analysis