TESTING LEVELS

• Unit Testing
• Integration Testing
• System Testing
• Regression Testing
• Acceptance Testing
 Unit Testing
• Unit testing is a testing in which the individual
unit of the software are tested in isolation
from other parts of a program.
Advantage :
• To catch the defects that occurs at the early
stage of software development.
• To minimize the ration of defects before
moving to next level

SKYTECH SYSTEMS
 Integration Testing
• Integration testing refers to the testing in
which software units of an application
combined and tested for a communication
interfaces between them.

Big Bang Testing

Bottom Up Testing
Top Down Testing
Sandwich
 Big Bang Testing
Module - 1

Module - 6 Module - 2

System

Module - 5 Module - 3

Module - 4

SKYTECH SYSTEMS
 Big Bang Testing
• A type of integration in which software
components of an application are
combined all at once into a overall system
according to this approach
Advantage :
• To check the data flow from one module to
another
• Communication between various modules
is checked
SKYTECH SYSTEMS
 Bottom-up Integration testing

• Bottom-up Integration testing :

In bottom up integration, all modules are added
or combined from lower level hierarchy to
higher level hierarchy I.e., the lower level
model is tested in isolation first, then the next
set of higher level modules are tested with the
previously tested lower modules.
• Worker modules are grouped into builds and
integrated.

SKYTECH SYSTEMS
 A
Bottom-up Integration

B C D

Test E
E F G

Test B, E, F

Test F

Test C Test
A, B, C, D,
E, F, G

Test G Test D,G

 Top-down Testing testing
• Test the top layer or the controlling
subsystem first
• Then combine all the subsystems that are
called by the tested subsystems and test the
resulting collection of subsystems
• Do this until all subsystems are incorporated
into the test
 A
Top-down Integration
B C D

E F G

Test
Test A Test A, B, C, D A, B, C, D,
E, F, G

Layer I Layer I + II All Layers

 Sandwich
Integration
 Sandwich
Integration
 Sandwich
Integration
 System Testing
• A system consists of all of the software
(and possibly hardware, user manuals,
training materials, etc.).
• System testing focuses on defects that
arise at this highest level of integration.
• Typically system : functionality, usability,
security, ..
 System Testing
After completing Unit and Integration testing
through white box testing techniques development
team release an .exe build (all integrated module) to
perform black box testing.

• Recovery Testing
• Usability Testing
• Functional Testing
• Performance Testing
• Security Testing
• Installation Testing
 Recovery Testing
 It is a system test that forces the software to fail in
a variety of ways and verifies that recovery is
properly performed.
 If recovery is automatic, reinitialization,
checkpointing mechanisms, data recovery and
restart are evaluated for correctness. If recovery
requires human intervention, the mean-time-to-
repair (MTTR) is evaluated to determine whether it
is within acceptable limits.
 Usability Testing
During this test, testing team concentrates on the user
friendliness of build interface. It consists of following sub
tests.

• User Interface Test: Ease of use (screens should be

understandable to operate by End User)

• Look & Feel :- attractive

• Speed in interface :- Less number of task to complete

task

• Manual Support Test :- Context sensitiveness of user

manual.
 Functional
Testing
• The process of checking the
behavior of the application.

• It is geared to functional
requirements of an
application.

• To check the correctness of

outputs.

• Data validation and

Integration i.e. inputs are
correct or not.
 Performance
Testing
• LOAD TESTING – Also Known as Scalability Testing. During
this test, test engineers execute application build under
customer expected configuration and load to estimate
performance.
• Load Testing is to verify that the system/application can handle the expected
number of transactions and to verify the system/application behaviour under
both normal and peak load conditions (no. of users).

• STRESS TESTING – During this test, Test engineers

estimates the peak load. To find out the maximum number of
users for execution of out application user customer expected
configuration to estimate peak load.

• DATA VOLUME TESING -- Testing team conducts this test to

find the maximum limit of data volume of your application.
 Performance
Testing
• Configuration testing • Environmental test
– Test the various software and hardware – Test tolerances for heat,
configurations humidity, motion, portability
• Compatibility test
• Quality testing
– Test backward compatibility with
existing systems – Test reliability, maintain-
ability & availability of the
• Timing testing system
– Evaluate response times and time
• Response testing
to perform a function
– Tests system’s response to
presence of errors or loss of
data.
 Performance
 Soak Testing: Testing
 Soak Testing is aka Endurance


Grey box testing
It is the combination of black-box
Testing. Running a system at high testing and white-box testing
load for a prolonged period of time  This can be applied if tester have
to identify the performance limited internal details of program
problems is called Soak Testing. It is
 Ad Hoc Testing/Negative testing/Gorilla
to make sure the software can
testing/Monkey testing
handle the expected load over a
 Testing the application randomly
long period of time.
without looking the requirement
 Spike Testing:  Testing performed without planning
 Spike Testing is to determine the and documentation
behaviour of the system under  The tests are intended to be run only
sudden increase of load (a large once, unless a defect is
number of users) on the system. discovered. Ad hoc testing is the least
formal test method.
 Performance
 Sanitary testing Testing  Smoke testing
 SMOKE TESTING, also known as
 Sanity testing is a subset of
“Build Verification Testing”, is a
regression testing. After receiving the type of software testing that
software build, sanity testing is comprises of a non-exhaustive set
performed to ensure that the of tests that aim at ensuring that
code changes introduced are the most important functions
working as expected . work. The result of this testing is
This testing is a checkpoint to used to decide if a build is stable
determine if testing for the build can enough to proceed with
proceed or not. further testing
 To make sure if the build we
 Done at “release level” to check
received from the development
main functionality without going team is testable or not
deeper  Known as “Day 0” check.
 Security Testing
 Testing how well the system protects
against unauthorized internal or
external access, willful damage, etc, may
require sophisticated testing techniques
 Security testing attempts to verify that
protection mechanisms built into a
system will, in fact, protect it from
improper penetration. During Security
testing, password cracking,
unauthorized entry into the software,
network security are all taken into
 Acceptance Testing
(Alpha $ Beta)
 A formal test conducted to determine
whether or not a system satisfies its
acceptance criteria and to enable the
customer to determine whether or not to
accept the system.
 It is the final test action before deploying the
software. The goal of acceptance testing is to
verify that the software is ready and can be
used by the end user to perform the functions
for which the software was built.
 Alpha Testing
1. The application is tested by the users who
doesn’t know about the application.
2. Done at developer’s site under controlled
conditions
3. Under the supervision of the developers.
 Beta Testing
1. This Testing is done before the final release of
the software to end-users.
2. Before the final release of the software is
released to users for testing where there will be
no controlled conditions and the user here is
free enough to do what ever he wants to do on
the system to find errors.
 Regression
Testing
 Testing with the intent of determining if
bug fixes have been successful and have
not created any new problems. Also, this
type of testing is done to ensure that no
degradation of baseline functionality has
occurred.
 The Testing Team

 Program Manager-
• The planning and execution of the project to ensure the success
of a project minimizing risk throughout the lifetime of the
project.
• Responsible for writing the product specification, managing the
schedule and making the critical decisions and trade-offs.

 QA Lead-
• Coach and mentor other team members to help improve QA
effectiveness
• Work with other department representatives to collaborate on
joint projects and initiatives
• Implement industry best practices related to testing automation
and to streamline the QA Department.
Test Analyst\Lead-
• Responsible for planning, developing and executing automated
test
systems, manual test plans and regressions test plans.
• Identifying the Target Test Items to be evaluated by the test
effort
• Defining the appropriate tests required and any associated Test

Data
• Gathering and managing the Test Data
• Evaluating the outcome of each test cycle

Test Engineer-
• Writing and executing test cases and Reporting defects
• Test engineers are also responsible for determining the best way
a
test can be performed in order to achieve 100% test coverage of
all
components
Top Software Testing Tools List

Wapt: Download Link:

https://www.loadtestingtool.com/download.shtml
Selenium
Download Link: https://www.selenium.dev/downloads/
(for selenium)
LambdaTest
TestComplete
Jmeter: Download link:
http://jmeter.apache.org/download_jmeter.cgi
LoadRunner
Browsershots
Webload: http://www.radview.com/webload-download/
Etc…
End of Lecture 5