SOFTWARE TESTING

A Seminar Report Submitted in partial fulfillment of the requirements

for the award of the degree of BCA in Big Data Analytics,Cloud
Computing & Cyber Security under Ms.Arphita
Yenepoya (deemed to be university).
by
Syed Mohammed farhan
Regd No : 20BDACC127

Under the Guidence of

Ms.Arphita
(Asst. Professor , Dept of computer Science)

DEPARTMENT OF COMPUTER SCIENCE

YIASCM Yenepoya (Deemed to be university)
11-2022
 1

CERTIFICATE

This is to certify that the seminar entitled “Software Testing” is

a work done by “Syed Mohammed Farhan”
Bearing Registration Number “20BDACC127”, of BCA (Big
data Analytics , Cloud Computing & cyber security) has been
completed successfully . This is a partial fulfillment of the of
Bachelor Degree in Computer Application under Yenepoya
(Deemed To Be University) , Mangalore . I Wish him
success in all future endeavours.

Ms. Arphita Mr. Narayana Sukumar

( Asst. professor, dept of (Dept Head of computer
Computer science ) science)
 2

Acknowledgments

I owe a lot to, my seminar guide Ms. Arphita for providing Competent
leadership Through out this effort . working with her has been a
compeletely different experience, and I want to thank her for all the
aid , advice , and talks.
I would like to thanks Mr. Narayana
Sukumar, who is the department Head for Computer Science at the
YENEPOYA INSTITUTE OF ARTS SCIENCE COMMERCE AND
MANAGEMENT.

Last but not the least, we would like to express our gratitude to
everyone who contributed , directly or indirectly , to the creation and
success of this seminar.

Syed Mohammed Farhan

Regd No : 20BDACC127
Department of Computer Science
 3

Abstract
The development of large software systems is a complex
and error prone process. Faults might occur at any
development stage and they must be identified and
removed as early as possible to stop their propagation
and reduce verification costs. Quality engineers must be
involved in the development process since the very early
phases to identify required qualities and estimate their
impact on the development process. Their tasks span
over the whole development cycle and go beyond the
product deployment through maintenance and post
mortem analysis. Developing and enacting an effective
quality process is not a simple task, but it requires that
we integrate many quality-related activities with product
characteristics, process organization, available resources
and skills, and budget constraints.
This paper discusses the main characteristics of a good
quality process, then surveys the key testing phases and
presents modern functional and model-based testing
approaches.

Signature of the student:

Name : Syed mohammed farhan

Regd no:20BDACC127

Semester :V semester

Branch: Department of computer science

Section: BCA (BIG DATA ANALYTICS)

Date:
 4

TABLE OF CONTENTS
content page no
Certificate 1

acknowledgments 2

abstract 3

Software testing 6

Why software testing is important 7

What is the need of testing 7-8

Benefits of testing 9-10

Types of software testing 10-19

Software testing principle 20-23

Levels of testing 24-27

conclusion 28

refrence 29
 5

FIGURES PAGE NO
TYPES OF SOFTWARE TESTING
11
MANUAL TESTING
13
Classification of manual testing
14
AUTOMATION TESTING
15
OTHER TYPES OF SOFTWARE TESTING
16
SOFTWARE TESTING PRINCIPLE
20
LEVELS OF TESTING
25
LIST OF FIGURES

SOFTWARE TESTING
 6

Software Testing is a method to check

whether the actual software product
matches expected requirements and to
ensure that software product is Defect free. It
involves execution of software/system
components using manual or automated
tools to evaluate one or more properties of
interest. The purpose of software testing is
to identify errors, gaps or missing
requirements in contrast to actual
requirements.
Some prefer saying Software testing
definition as a White Box and Black Box
Testing. In simple terms, Software Testing
means the Verification of Application Under
Test (AUT). This Software Testing course
introduces testing software to the audience
and justifies the importance of software
testing.
 7

Why Software Testing is Important?

Software Testing is Important because if there

are any bugs or errors in the software, it can be
identified early and can be solved before delivery
of the software product. Properly tested software
product ensures reliability, security and high
performance which further results in time saving,
cost effectiveness and customer satisfaction.

What is the need of Testing?

Testing is important because software bugs

could be expensive or even dangerous.
Software bugs can potentially cause
monetary and human loss, and history is full
of such examples.
 8

 n April 2015, Bloomberg terminal in London

crashed due to software glitch affected more than
300,000 traders on financial markets. It forced the
government to postpone a 3bn pound debt sale.
 Nissan cars recalled over 1 million cars from the
market due to software failure in the airbag
sensory detectors. There has been reported two
accident due to this software failure.
 Starbucks was forced to close about 60 percent of
stores in the U.S and Canada due to software
failure in its POS system. At one point, the store
served coffee for free as they were unable to
process the transaction.
 Some of Amazon’s third-party retailers saw their
product price is reduced to 1p due to a software
glitch. They were left with heavy losses.
 Vulnerability in Windows 10. This bug enables
users to escape from security sandboxes through
a flaw in the win32k system.
 In 2015 fighter plane F-35 fell victim to a software
bug, making it unable to detect targets correctly.
 China Airlines Airbus A300 crashed due to a
software bug on April 26, 1994, killing 264
innocents live
 In April of 1999, a software bug caused the failure of a
$1.2 billion military satellite launch, the costliest
accident in history
 9

BENEFITS OF SOFTWARE TESTING

 Cost-Effective: It is one of the important

advantages of software testing. Testing any IT
project on time helps you to save your money for
the long term. In case if the bugs caught in the
earlier stage of software testing, it costs less to
fix.

 Security: It is the most vulnerable and sensitive

benefit of software testing. People are looking for
trusted products. It helps in removing risks and
problems earlier.

 Product quality: It is an essential requirement of

any software product. Testing ensures a quality
product is delivered to customers.
 Customer Satisfaction: The main aim of any
product is to give satisfaction to their customers.
UI/UX Testing ensures the best user experience.
 10

Types of Software Testing

In this section, we are going to understand the

various types of software testing, which can be
used at the time of the Software Development Life
Cycle.

As we know, software testing is a process of

analyzing an application's functionality as per the
customer prerequisite.

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.

The categorization of software testing is a part of

diverse testing activities, such as test strategy,
test deliverables, a defined test objective, etc.
And software testing is the execution of the
software to find defects

The purpose of having a testing type is to confirm

the AUT (Application Under Test)
 11

To start testing, we should have a requirement,

application-ready, necessary resources available. To
maintain accountability, we should assign a respective
module to different test engineers
 12

The software testing mainly divided into two parts, which are as
follows:

o Manual Testing
o Automation Testing

MANUAL TESTING

Testing any software or an application according to the

client's needs without using any automation tool is
known as manual testing.

In other words, we can say that it is a procedure

of verification and validation. Manual testing is used
to verify the behavior of an application or software in
contradiction of requirements specification.
 13

We do not
require any
precise
knowledge
of any testing tool
to execute the
manual test
cases. We can
easily prepare the
test document
while performing manual testing on any application.

Classification of Manual Testing

In software testing, manual testing can be further

classified into three different types of testing, which
are as follows:

o White Box Testing

o Black Box Testing
o Grey Box Testing
 14

White Box Testing

In white-box testing, the developer will inspect every line
of code before handing it over to the testing team or
the concerned test engineers.

In other words, we can say that the developer will

execute the complete white-box testing for the
particular software and send the specific application to
the testing team.

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 .
 15

Black Box Testing

Another type of manual testing is black-box testing. In
this testing, 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, do one
round of White box
testing, and send it to
the testing team.

Here, fixing the bugs

means the defect is
resolved, and the
particular feature is
working according to the given requirement.

Grey Box Testing

Another part of manual testing is Grey box testing. It
is a collaboration of black box and white box testing.

Since, the grey box testing includes access to internal

coding for designing test cases. Grey box testing is
performed by a person who knows coding as well as
testing.
 16

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.
It provides combined benefits of both black box testing and
white box testing both

It combines the input of developers as well as testers and

improves overall product quality

It reduces the overhead of long process of testing functional

and non-functional types

Automation Testing
The most significant part of Software testing is
Automation testing. It uses specific tools to automate
manual design test cases without any human
interference.
 17

Automation testing is the best way to enhance the

efficiency, productivity, and coverage of Software
testing.

It is used to re-run the test scenarios, which were

executed manually, quickly, and repeatedly.

In other words,
we can say that
whenever we
are testing an
application
by using some
tools is known
as au tomation
testing.
 18

Some other types of Software Testing

In software testing, we also have some other types of
testing that are not part of any above discussed testing,
but those testing are required while testing any software
or an application.

o Smoke Testing
o Sanity Testing
o Regression Testing
o User Acceptance Testing
o Exploratory Testing
o Adhoc Testing
o Security Testing
o Globalization Testing
 19

Smoke Testing
In smoke testing, we will test an application's basic and critical features
before doing one round of deep and rigorous testing.

Or before checking all possible positive and negative values is known

as smoke testing. Analyzing the workflow of the application's core and
main functions is the main objective of performing the smoke testing.

Sanity Testing
It is used to ensure that all the bugs have been fixed and no added
issues come into existence due to these changes. Sanity testing is
unscripted, which means we cannot documented it. It checks the
correctness of the newly added features and components .

Regression Testing
Regression testing is the most commonly used type of software testing.
Here, the term regression implies that we have to re-test those parts of
an unaffected application.

Regression testing is the most suitable testing for automation tools. As

per the project type and accessibility of resources, regression testing can
be similar to Retesting.

Whenever a bug is fixed by the developers and then testing the other
features of the applications that might be simulated because of the bug
fixing is known as regression testing.

In other words, we can say that whenever there is a new release for some
project, then we can perform Regression Testing, and due to a new
feature may affect the old features in the earlier releases.
 20

User Acceptance Testing

The User acceptance testing (UAT) is done by the individual
team known as domain expert/customer or the client. And
knowing the application before accepting the final product is
called as user acceptance testing.

In user acceptance testing, we analyze the business scenarios,

and real-time scenarios on the distinct environment called
the UAT environment. In this testing, we will test the
application before UAI for customer approval.

Exploratory Testing
Whenever the requirement is missing, early iteration is required,
and the testing team has experienced testers when we have a
critical application. New test engineer entered into the team
then we go for the exploratory testing.

To execute the exploratory testing, we will first go through the

application in all possible ways, make a test document,
understand the flow of the application, and then test the
application.

Adhoc Testing
Testing the application randomly as soon as the build is in the
checked sequence is known as Adhoc testing.

It is also called Monkey testing and Gorilla testing. In Adhoc

testing, we will check the application in contradiction of the
client's requirements; that's why it is also known as negative
testing.
 21

When the end-user using the application casually, and he/she

may detect a bug. Still, the specialized test engineer uses the
software thoroughly, so he/she may not identify a similar
detection.

Security Testing
It is an essential part of software testing, used to determine the
weakness, risks, or threats in the software application.

The execution of security testing will help us to avoid the nasty

attack from outsiders and ensure our software applications'
security.

In other words, we can say that security testing is mainly used

to define that the data will be safe and endure the software's
working process.

Globalization Testing
Another type of software testing is Globalization
testing. Globalization testing is used to check the developed
software for multiple languages or not. Here, the
words globalization means enlightening the application or
software for various languages.

Globalization testing is used to make sure that the application

will support multiple languages and multiple features .

In present scenarios, we can see the enhancement in

several technologies as the applications are prepared to
be used globally
 22

Software Testing Principles

Software testing is a procedure of implementing

software or the application to identify the defects or
bugs. For testing an application or software, we need to
follow some principles to make our product defects free,
and that also helps the test engineers to test the
software with their effort and time. Here, in this section,
we are going to learn about the seven essential
principles of software testing.
 23

Testing shows the presence of defects

The test engineer will test the application to make sure that the
application is bug or defects free. While doing testing, we can
only identify that the application or software has any errors. The
primary purpose of doing testing is to identify the numbers of
unknown bugs with the help of various methods and testing
techniques because the entire test should be traceable to the
customer requirement, which means that to find any defects
that might cause the product failure to meet the client's needs.

Exhaustive Testing is not possible

Sometimes it seems to be very hard to test all the modules and
their features with effective and non- effective combinations of
the inputs data throughout the actual testing process.

Hence, instead of performing the exhaustive testing as it takes

boundless determinations and most of the hard work is
unsuccessful. So we can complete this type of variations
according to the importance of the modules because the
product timelines will not permit us to perform such type of
testing scenarios.

Early Testing
Here early testing means that all the testing activities should
start in the early stages of the software development life
cycle's requirement analysis stage to identify the defects
because if we find the bugs at an early stage, it will be fixed in
the initial stage itself, which may cost us very less as compared
to those which are identified in the future phase of the testing
process.
 24

To perform testing, we will require the requirement

specification documents; therefore, if the requirements are
defined incorrectly, then it can be fixed directly rather than
fixing them in another stage, which could be the development
phase.

Defect clustering
The defect clustering defined that throughout the testing
process, we can detect the numbers of bugs which are
correlated to a small number of modules. We have various
reasons for this, such as the modules could be complicated; the
coding part may be complex, and so on.

These types of software or the application will follow

the Pareto Principle, which states that we can identify that
approx. Eighty percent of the complication is present in 20
percent of the modules. With the help of this, we can find the
uncertain modules, but this method has its difficulties if the
same tests are performing regularly, hence the same test will
not able to identify the new defects.

Pesticide paradox
This principle defined that if we are executing the same set of
test case again and again over a particular time, then these
kinds of the test will not be able to find the new bugs in the
software or the application. To get over these pesticide
paradoxes, it is very significant to review all the test cases
frequently. And the new and different tests are necessary to be
written for the implementation of multiple parts of the
application or the software, which helps us to find more bugs.
 25

Testing is context-dependent
Testing is a context-dependent principle states that we
have multiple fields such as e-commerce websites,
commercial websites, and so on are available in the
market. There is a definite way to test the commercial
site as well as the e-commerce websites because every
application has its own needs, features, and
functionality. To check this type of application, we will
take the help of various kinds of testing, different
technique, approaches, and multiple methods ..Therefore,
the testing depends on the context of the application.

Absence of errors fallacy

Once the application is completely tested and there are
no bugs identified before the release, so we can say that
the application is 99 percent bug-free.But there is the
chance when the application is tested beside the
incorrect requirements, identified the flaws, and fixed
them on a given period would not help as testing is
done on the wrong specification, which does not apply
to the client's requirements. The absence of error fallacy
means identifying and fixing the bugs would not help if
the application is impractical and not able to accomplish
the client's requirements and needs.
 26

Levels of Testing

In this section, we are going to understand the

various levels of software testing.

As we learned in the earlier section of the software

testing tutorial that testing any application or software,
the test engineer needs to follow multiple testing
techniques.

In order to detect an error, we will implement software

testing; therefore, all the errors can be removed to find a
product with more excellent quality.

What are the levels of Software Testing?

Testing levels are the procedure for finding the missing
areas and avoiding overlapping and repetition between
the development life cycle stages. We have already seen
the various phases such as Requirement collection,
designing, coding testing, deployment, and
maintenance of SDLC.

In order to test any application, we need to go through

all the above phases of SDLC. Like SDLC, we have
multiple levels of testing, which help us maintain the
quality of the software.
 27

Different Levels of Testing

The levels of software testing involve the different
methodologies, which can be used while we are
performing the software testing.

In software testing

, we have four different levels of testing, which are as

discussed below:
1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing
 28

Level1: Unit Testing

Unit testing is the first level of software testing, which is used
to test if software modules are satisfying the given requirement
or not.

The first level of testing involves analyzing each unit or an

individual component of the software application.

Unit testing is also the first level of functional testing

. The primary purpose of executing unit testing is to validate unit

components with their performance.

Level2: Integration Testing

The second level of software testing is the integration
testing. The integration testing process comes after unit
testing.

It is mainly used to test the data flow from one module or

component to other modules.

In integration testing, the test engineer tests the units or

separate components or modules of the software in a group.

The primary purpose of executing the integration testing is to

identify the defects at the interaction between integrated
components or units.

When each component or module works separately, we need to

check the data flow between the dependent modules, and this
process is known as integration testing.
 29

Level3: System Testing

The third level of software testing is system testing, which is
used to test the software's functional and non-functional
requirements.

It is end-to-end testing where the testing environment is

parallel to the production environment. In the third level of
software testing, we will test the application as a whole
system.

To check the end-to-end flow of an application or the software

as a user is known as System testing.

Level4: Acceptance Testing

The last and fourth level of software testing is acceptance
testing, which is used to evaluate whether a specification or the
requirements are met as per its delivery.

The software has passed through three testing levels (Unit

Testing, Integration Testing, System Testing). Some minor
errors can still be identified when the end-user uses the system
in the actual scenario.

In simple words, we can say that Acceptance testing is

the squeezing of all the testing processes that are
previously done.

The acceptance testing is also known as User acceptance

testing (UAT) and is done by the customer before accepting
the final product.
 30

CONCLUSION

Software testing is an important part of the software

development process. It is not a single activity that
takes place after code implementation, but is part of
each stage of the lifecycle. A successful test strategy
will begin with consideration during requirements
specification. Testing details will be fleshed through
high and low level system designs, and testing will be
carried out by developers and separate test groups after
code implementation.
As with the other activities in the software lifecycle,
testing has its own unique challenges. As software
systems become more and more complex, the
importance of effective, well planned testing efforts
will only increase.
 31

REFERENCE

GEEKS FOR GEEKS

JAVATPOINT
TECH TARGET
GURU99
 32

THANK YOU
FOR
YOUR
SUPPORT