Abstract area, which includes numerous other technical and

Abstract – Software testing
is an exceptionally wide area, which includes numerous other technical and
non-technical areas, for example, determination, plan and execution, support, procedure
and maintenance problems in Software designing. This concentrates on the
cutting edge in testing methods, and furthermore, the latest methods, which
signify the future, course of this zone.

Software testing is a procedure of checking
and approving a product application meets the professional and technical
requirements that conducted its design, advancement and acts of course and
distinguishes imperative mistakes. We test software by choosing suitable
testing method and applying them logically. Software testing procedures are
different techniques to do software testing. Testing techniques suggest to
various techniques for testing specific highlights a PC program, system or
item. We need to ensure that we select technique(s) that will ensure the most
proficient and successful testing of the system. Test techniques should
discover most prominent conceivable number of errors with reasonable measure of
actions connected over a sensible time navigate with a limited number of cases.
A few methods are simple; others require a little ordeal to truly utilize sufficiently.
Testing can be expensive however not testing software may be extra expensive. Software
testing goes for accomplishing certain an objectives and standards, which are
to be taken after. Software Testing can be measured as a difficult effort. The
essential object within testing process the software tester follow that how to reduce
a big number of tests into sensible tests set.

Keywords – Need for Software Testing, Objective of
Software Testing, Techniques for Software Testing, Black Box Testing, White Box
Testing, Grey Box Testing, Dynamic Testing, Static Testing.


The aim of testing is verification,
validation and error detection identification with a specific end goal to
discover issues and the purpose behind finding these issues is to get them fixed.
Software testing is more than error identification. Testing software is working
on software to Verify that it performs “as identified”; to Detect
Errors, and to Validate that what has been resolved is the thing
that the customer really needed.

Verification: Verification is the testing or checking
of data, containing software design, for conformance and uniformity by
assessing the outcomes against pre-indicated requests.

Detection: Testing must
be purposefully effort to make things to turn out seriously to choose whether
things occur when they should not or things do not occur when they should.

3.      Validation: Validation looks at the system perfection. It
is a way to inspection that what has been specified that the client really


There are some
common software issues are inappropriate calculations, inappropriate
data edit, useless data edits, incorrect coding, insufficient software performance, false/unclear data, difficulty
using of software, outdated software’s, unreliable processing, difficulty to


testing is required to validate and verify that the software that has been
built for required conditions. If we want to save time, money and provide
customers with better user experience then we will use software testing. If not
we may maybe loose our customer. So keeping in mind the end goal to ensure,
that we give our customer a legitimate software arrangement, we go for testing.
Testing confirms that what you get at last is the thing that you needed to build.
If there is any issue, any mistake in the system, which can make software
unusable by the customer. These assistances in the avoidance of faults in a


Some objectives
of the software development are:

Validation and

Testing of
software used for validation and verification a software.


Testing must
be finished in proficient and viable strategy inside the financial plan and


process must balance the necessities, technical constraints and client desire.


Documents must
be prepared of failure and success of testing procedure. So no compelling
reason to test once more.


We should know
what we are doing, what we are concentrating on and what will be the
conceivable outcome.


Software testing techniques is a way to find
errors/bugs and measure the quality of developed software. There are different
methods or techniques used to check performance and quality of a software.
However, White and Black Box Testing are two main software-testing techniques.

Black box testing: This technique is detail based testing, this
strategy concentrates on output. Testers are not concerned with internal
components. They just checked the product does what it should. Learning of
coding is not vital, and testers work at UI level. The tester along these lines
has to recognize what the part of the system is, and its functionalities,
however does not know its inside systems. He has a “client” profile.
Testers are searching for incorrect or missing functions interface, execution,
program introduction and leave blunders; information structure or outside
database get to mistakes.



Black box
testing is reproducible


Neutral tests because the designer and
tester work individually

Test cases
are difficult to design

Tester is
free from any burden of knowledge of
particular programming languages to test the consistency and functionality

Results are
frequently miscalculated

Test always
executed from user point of view

reason is not found

May be
non-technical but used in large systems

Not used in
complex segments of code

White-box testing: This technique utilizes
coding knowledge as a major aspect of the test system. At the point when an
item comes up short, testers dive as deep into code as important to discover
the reason. The software designer do this without anyone else’s help then he
decide how the product would work. Two other names of this technique are Structure
based and Glass box testing. All of the inner segments of the software or
application are test through the source code, primary work base of the tester.
He should have a global perspective of the working of the application. Not at
all like in “Black box” testing, the tester has a
“developer” profile, not a “client” profile. By making a
“white box” test, the tester can see which code line is required
every usefulness. It permits to test the information flow, and the handling of
exemptions and errors.



Help in improving the code and evaluating all the loops and paths

Difficult to proceed white-box testing
because it needs specific tools

Spare lines can be removed

Missed out
the cases omitted in the code

Test cases can be simply automated

White box testing is  time consuming method

carefully gives reason about implementation

Sometimes a modification
in code may be necessary and thus all the cases may need to be tested again.

It finds error in the
hidden code

White box testing is a broad

Testing: Grey box testing is a strategy to test the application with having
constrained data of the internal workings of an application. In software
testing, the expression the more you
know, the better conveys a considerable measure of weight while testing an
application.  It is not like Black Box testing, where the analyzer only tests the
application’s User Interface; in Grey box testing, the analyzer have approaches
to designed database and reports. In this type of tests, the tester knows the
part of the system and of its functionalities, and furthermore knows it is
inside components the interior information structure and the calculations
utilized. In addition, he does not approach the source code. Obviously, the
“Grey Box” strategy for the most part joins favorable circumstances
from the “White Box” and “Black Box” methods. These tests
should hardly be done during the developing phase of a software, since it
infers tests on the programm’s functionalities; it subsequently must be in a
state near the last one for these tests to be applicable. Without a doubt, amid
“Grey Box” testing, testers mainly use “Black box”
techniques, since the source code isn’t available



Grey box testing offers combined advantage
of both Black box testing and White box testing.

Not good for algorithm testing

Grey box testers depend on
functional details and interface definition

Tests can be terminated if the software designer has already run a
test case.

It can design good test cases around
communication protocol

Capability to go over the
code and test coverage is limited

Testing will be performed user point of

Testing every possible
input stream is unrealistic 

Testing is complete on the basis of data
flow diagram and high level database

Limited information of the
internal workings of an application

Difference of Black, White and Grey Box

Black Box Testing

White Box Testing

Grey Box Testing

Internal working of an application need not be known

Tester has full knowledge about internal working

Tester has limited knowledge about internal working

extensive and slow

extensive and slow

Partly extensive and slow

Not suitable
for algorithm

Suitable for

Not suitable
for algorithm

It executed
by tester, developer and end user

It executed
by tester, developer

It executed
by tester, developer and end user

depends on external special cases

working is completely known

Testing configuration
depends on high level database diagrams

Static testing:
Testers inspect the product’s code and documentation yet do not perform the
program. Static tests begin right on time in the product’s advancement during
the check procedure. It should be possible physically. This kind of testing
checks the code, prerequisite reports and configuration documents and puts
feedback on the work record. At the point when the product is non operational
and inactive, we perform security testing to test the product in non-runtime
condition. With static testing, we attempt to discover the errors, code defects
and conceivably noxious code in the software application.



Helps in identifying the faults in code

Time consuming

Easy and fast technique to fix and find an

Only scan
the codes

To conduct testing, need a good developer

1.       Automated
tools may provide false positives and false negatives

Used automated tool for testing

Automated tools work with some programming

Possible to find error in early stage

Not Identify weak points

Dynamic testing: The product is executed with different
sources of info and testers compare outputs with projected conduct with this
method. Dynamic testing is done when the code is in operation mode. Dynamic
testing is performed in runtime condition. At the point when the code being
executed is contribution with a value, the output of the code is checked and
compared with the expected output. With this we can watch the functional
behavior of the software, CPU reaction time, execution of the performance of
the system. Dynamic testing is also called validation testing.



Helps to identify weak areas

Automated tools may give a
false security

Support analysis of application

1.       Costly to fix the errors

Applied with any application

2.       Not easy to find a trained professional for dynamic testing

Validating static code
analysis findings

Tough to follow the weakness in the code

Identifying weak areas in
a run-time environment

More time to resolve the issues


We can describe software testing as an activity
aimed at ability of a program to determine, that it meets its required
specification. Software testing can give a free perception of the product to empower
the business to recognize and comprehend the danger of programming usage.
Testing is the most basic piece of the Software Development Lifecycle, as it is
something whereupon the last conveyance of the item is reliant. It can improve
the current testing strategies, both for time adequacy and in addition, for
effective and solid last item which meets the predefined necessities as well as
additionally furnishes with most extreme operational effectiveness. Testing
is an endless procedure and it demonstrates the event of mistakes not the
non-appearance. We should certify the software testing
procedure viability and effectiveness for real software, and afterward we can put
these testing methods.

Written by