Software Testing

Ø Software testing is:

§ a process of identifying the correctness of
software by considering its all attributes (Reliability,
Scalability, Portability, Re-usability, Usability)
§ Evaluating the execution of software components
to find the software bugs or defects.
 Wh
Organizing for Software Testing a. A
b. A
by c
Ø Independent Test Group (ITG) c. A
d. A
Ø The ITG is part of the software development project Ans
team. soft

Ø The software development team is always Wh

soft
responsible for: a. T
b. T
§ Testing the individual units (components) of the c. T
program, d. T

§ Ensuring that each performs the function for Ans

which it was designed. Wh

a. In
b. In
c. In
d. In
Organizing for Software Testing

Ø However, you don‘t turn the program over to ITG

and walk away.
Ø While testing is conducted, the developer must be
available to correct errors that are uncovered.

Ø The developer and the ITG work closely throughout

a software project to ensure that thorough tests will
be conducted.
Types of Software Testing

Ø If we want to ensure that our software is bug-free or

stable, we must perform the various types of
software testing because testing is the only method
that makes our application bug-free.
Types of Software Testing
Types of Software Testing

What is Manual Testing?

§ Testing any software or an application according to the client's
needs without using any automation.
§ it is a procedure of Verification and Validation.
Classification of Manual Testing

Manual testing can be further classified into three

different types of testing, which are as follows:

§ White Box Testing

§ Black Box Testing
§ Grey Box Testing
White Box Testing (The source code is visible)

In white-box testing, the developer will inspect every line

of code before handing it over to the testing team .
White box testing is also known as open box testing.

The purpose of implementing the white box testing:

is to emphasize the flow of inputs and outputs over the
software and enhance the security of an application.
Black Box Testing (The source code is not visible)

Black box testing is:

§ the test engineer will analyze the software against
requirements, identify the defects or bug, and sends it
back to the development team.
§ Then, the developers will fix those defects, and send it to
the testing team again.
Black Box Testing

§ The source code is not visible in this testing; that's why it

is known as black-box testing.
 What is white-b
Types of Black Box Testing a. A testing me
against require
b. A testing me
Black box testing further categorizes into two parts: before handing
c. A testing me
§ Functional Testing d. A testing me
against require
§ Non-function Testing Answer: b. A te
of code before

What is anothe
a. Open box tes
b. Closed box t
c. Black box tes
d. Gray box tes
Answer: a. Ope

What is the pur

a. To analyze th
b. To identify d
c. To emphasize
d. To enhance t
Answer: c. To e
Functional Testing

Ø Functional testing is also known as Component

testing.
Ø The test engineer will check all the components
systematically against requirement specifications ,
Ø and ensure that each performs the function for
which it was designed.
Types of Functional Testing

§ Unit Testing
§ Integration Testing
§ System Testing
1. Unit Testing

§ The test engineer will test the smallest unit of

software or module of an application independently.
§ The primary objective of executing the unit testing is
to confirm the unit components with their
performance.
 a. A testing method where
systematically against requ
2. Integration Testing b. A testing method where
software or module of an a
c. A testing method where
dependent modules or int
est the data flow between dependent d. A testing method where
ules or interface between two features. between each module
: a. A testing metho
purpose of executing the integration testing is components systematically
st the statement's accuracy between each
ule
What is another name for
a. Unit testing
b. Integration testing
c. Component testing
d. System testing
: c. Component tes

What is the objective of un

a. To test the smallest unit
independently
b. To test the data flow bet
two features
c. To test the statement's a
d. To test the overall funct
1. Unit Testing Explanation Example

1 0
0
0 0

1 1
1

2. Integration Testing
1 0
0

1 1
?
0
Types of Integration Testing

§ Incremental Testing
§ Non-Incremental Testing
Incremental Integration Testing

§ Suppose, we take two modules and analysis the data

flow between them if they are working fine or not.
§ If these modules are working fine, then we can add
one more module and test again. And we can continue
with the same process to get better results.
Types of Incremental Integration Testing

§ Top-down Incremental Integration Testing

§ Bottom-up Incremental Integration Testing
1. Top-down Incremental Integration Testing
Ø In this approach, we will add the modules step by step
or incrementally and test the data flow between them.
Ø We have to ensure that the modules we are add is
the child of the earlier ones (previous modules).

up Incremental Integration
m-up approach, we will add the modules
y and check the data flow between
ensure that the module we add is
of the earlier ones (previous modules).
What should be ensured while adding mo
down approach?
a. The modules added should be children
b. The modules added should be parents
c. The modules added should not be rela
ones
d. The modules added should be tested i
: a. The modules added should be
earlier ones
What should be ensured while adding mo
bottom-up approach?
a. The modules added should be children
b. The modules added should be parents
c. The modules added should not be rela
ones
d. The modules added should be tested i
: b. The modules added should be
earlier ones
Which approach adds modules step by st
data flow between them?
a. Top-down approach
b. Bottom-up approach
c. Both top-down and bottom-up approa
Non-Incremental Integration Testing/
Big Bang Method
Ø Whenever the data flow is complex and very difficult to
classify a parent and a child, we will go for the non-
incremental integration approach.
Ø The non-incremental method is also known as the Big
Bang method.
 What is
a. Top-d
3. System Testing b. Botto
c. Big Ba
d. Both
:
§ Whenever we are done with the unit and When is
integration testing, we can proceed with the a. When

system testing.
b. When
a child
§ In system testing, the test environment is parallel c. When
d. When
to the production environment. It is also known :
parent a
as end-to-end testing.
What is
a. To tes
indepen
b. To tes
between
c. To tes
d. To tes
:
deploye
Software Testing Strategy --The Big Picture

System test
Software Testing Strategy —Spiral Test Model
 a. Int
b. Sys
Software Testing Strategy —Spiral Test Model c. Un
d. Val
Ø Testing progresses is actually a series of four steps that are
implemented sequentially: What
§ Unit testing, tests focus on each component of the software a. De
as implemented in source code. b. Val
c. Tes
§ Integration testing: where the focus is on design and the code
construction of the software architecture. d. Tes

§ Validation Testing: where requirements established as part sourc

of requirements modeling are validated against the software
What
that has been constructed. a. De
§ Finally, you arrive at system testing, where the software and b. Val
c. Tes
other system elements are tested as a whole. code
d. Tes

What
a. De
Non-function Testing

§ It provides detailed information on software product

performance and used technologies.
§ Non-functional testing will help us minimize the risk of
production and related costs of the software.
§ Non-functional testing is a combination of performance,
load, stress, usability and, compatibility testing.
Types of Non-function Testing

§ Performance Testing
§ Usability Testing
§ Compatibility Testing
Types of Non-function Testing

1- Performance Testing:
§ In this type of non-functional testing, the test
engineer will only focus on several aspects, such
as Response time, Load, scalability, and Stability of
the software or an application.
Types of Non-function Testing

Classification of Performance Testing

§ Load Testing
§ Stress Testing
§ Scalability Testing
§ Stability Testing
2. Usability Testing

Ø In usability testing, we will analyze the user-friendliness

(‫ ) دختس ها ةلوهس‬of an application and detect the bugs in the
software's end-user interface.
Ø the term user-friendliness defines the following aspects of
an application:
§ The application should be easy to understand, which
means that all the features must be visible to end-users.
§ The application's look and feel should be good that
means the application should be pleasant looking and
make a feel to the end-user to use it.
 a. To ana
3. Compatibility Testing b. To che
software
c. To tes
d. To tes
Ø In compatibility testing, we will check the functionality of an :
application in specific hardware and software environments. and soft
§ Software, means we can test the application on the What co
different operating systems and other browsers, a. Only s
b. Only h
§ Hardware, means we can test the application on differentc. Both s
sizes. d. Neith
:

What is
a. To ana
b. To che
software
c. To tes
d. To tes
:

What ar
a. The a
Grey Box Testing

§ Grey box testing. It is a collaboration of black box

and white box testing.
§ In other words, we can say that if a single-person team done
both white box and black-box testing, it is considered grey
box testing.
Automation Testing

§ It uses specific tools to automate manual design test cases

without any human interference.
§ Automation testing is the best way to enhance the efficiency,
productivity, and coverage of Software testing.