System Testing

BSCS-FA17-052 NAME : UMAIR SECTION(A)

BSCS-FA17-142 NAME : SEEMAB SECTION(A)
BSCS-FA17-149 NAME : MUSAB SECTION(A)
What is System Testing?

 System Testing is the testing of a complete and fully

integrated software product. Usually, software is only one element of a larger
computer-based system. Ultimately, software is interfaced with other
software/hardware systems. System Testing is actually a series of different tests
whose sole purpose is to exercise the full computer-based system.
Category of Software Testing
 1. Black Box Testing
 2. White Box Testing
 Black-box testing
 is a method of software testing that examines the functionality of an application
without peering into its internal structures or workings. This method of test can be
applied virtually to every level of software
testing: unit, integration, system and acceptance. It is sometimes referred to as
specification-based testing.
 White box testing
 is the testing of the internal workings or code of a software application
What do you verify in System Testing?
 Testing the fully integrated applications including external peripherals in order to
check how components interact with one another and with the system as a whole.
This is also called End to End testing scenario.
 Verify thorough testing of every input in the application to check for desired
outputs.
 Testing of the user's experience with the application.
Software Testing Hierarchy
Software Testing Hierarchy

 Unit testing - testing performed on each module or block of code during

development. Unit Testing is normally done by the programmer who writes the code.

Integration testing - testing done before, during and after integration of a new module
into the main software package. This involves testing of each individual code module. One
piece of software can contain several modules which are often created by several different
programmers. It is crucial to test each module's effect on the entire program model.

System testing - testing done by a professional testing agent on the completed software
product before it is introduced to the market.

Acceptance testing - beta testing of the product done by the actual end users.
 Performance Testing

1. Introduction
2. What to focus upon?
Introduction
Performance testing non function technique performed to
determine the system parameters in term of responsiveness
and stability under various workload
Performance testing measures the quality attribute of the
system , such as scalability,reliability and resource usage.

Performance testing uncover what need to be improve

before the product goes to market
Introduction

 Performance testing is testing that is performed to determine how fast some aspect of a
system performed under a particular workload

 Performance testing uncover what need to be improve before the product goes to
market
What to focus upon?

Speed Determine whether the application response quickly

 Scalability Determine maximum user load the software application can handle.

Stability Determine if the application is stable under varying loads

STRESS TESTING
 Stress testing is carried out to check the behavior of the system under the sudden
increased load

 Stress Testing is defined as a type of Software Testing that verified the stability &
reliability of the system

 stress testing is to determine the limit, at which the system or software or

hardware breaks.
Introduction
 It ensures the security of the system under the failures

 Stress testing is performed by increasing the load suddenly.

 EXAMPLE
stressed when 5GB data is copied from the website and pasted in notepad. Notepad is
under stress and gives 'Not Responded' error message..
Alpha & beta Testing
Alpha testing
 The alpha testing Is conduct at developers end.
 It is performed in environment controlled by developers.
 It is performed before s/w is released to end users.
 The developers keeps of all the errors and problems.
 It involve both black box and white box testing
Beta testing
 The beta testing is conduct at users place
 It is performed in environment which is not controlled by developer.
 It is performed after releasing the s/w to end users.
 The end users record the problems & errors. Later report to developer.
 It involve only black box testing