0% found this document useful (0 votes)
20 views5 pages

Unit 3 STPM 5it5-12 2023

Uploaded by

Diya Pathak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views5 pages

Unit 3 STPM 5it5-12 2023

Uploaded by

Diya Pathak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Software Testing and Project Management - 5IT5 – 12

UNIT 3
 What is Black box Testing?
Black-box testing is a method of software testing that examines the
functionality of an application based on the specifications. It is also known as
Specifications based testing. Independent Testing Team usually performs this
type of testing during the software testing life cycle.
In this method, tester selects a function and gives input value to examine its
functionality, and checks whether the function is giving expected output or
not. If the function produces correct output, then it is passed in testing,
otherwise failed. The test team reports the result to the development team
and then tests the next function. After completing testing of all functions if
there are severe problems, then it is given back to the development team for
correction.
This method of test can be applied to each and every level of software testing
such as unit, integration, system and acceptance testing.
There are different techniques involved in Black Box testing.
 Equivalence Class
 Boundary Value Analysis
 Decision Tables
 State Transition
 Use Case
 All-pairs testing

o Equivalence Class - Equivalence partitioning is a technique of software


testing in which input data divided into partitions of valid and invalid
values, and it is mandatory that all partitions must exhibit the same
behaviour.

o Boundary Value Analysis - Boundary Value Technique is used to test


boundary values, boundary values are those that contain the upper and
lower limit of a variable. It tests, while entering boundary value whether
the software is producing correct output or not.

o Decision Table - Decision Table Technique is a systematic approach


where vario us input combinations and their respective system

UNIT-3 Page 1
Software Testing and Project Management - 5IT5 – 12

behaviour are captured in a tabular form. It is appropriate for the


functions that have a logical relationship between two and more than
two inputs.

o State Transition -State Transition Technique is used to capture the


behaviour of the software application when different input values are
given to the same function. This applies to those types of applications
that provide the specific number of attempts to access the application.

o Use Case -Use case Technique used to identify the test cases from the
beginning to the end of the system as per the usage of the system. By
using this technique, the test team creates a test scenario that can
exercise the entire software based on the functionality of each function
from start to end.

o All-Pair Testing -All-pair testing Technique is used to test all the possible
discrete combinations of values. This combinational method is used for
testing the application that uses checkbox input, radio button input, list
box, text box, etc.

 What is White Box Testing?

White Box Testing is a testing technique in which software’s internal structure,


design, and coding are tested to verify input-output flow and improve design,
usability, and security. In white box testing, code is visible to testers, so it is
also called Clear box testing, Open box testing, Transparent box testing, Code-
based testing, and Glass box testing.
It is one of two parts of the Box Testing approach to software testing. Its
counterpart, Blackbox testing, involves testing from an external or end-user
perspective. On the other hand, White box testing in software engineering is
based on the inner workings of an application and revolves around internal
testing.
The term “Whitebox” was used because of the see-through box concept. The
clear box or Whitebox name symbolizes the ability to see through the
software’s outer shell (or “box”) into its inner workings. Likewise, the “black

UNIT-3 Page 2
Software Testing and Project Management - 5IT5 – 12

box” in “Black Box Testing” symbolizes not being able to see the inner workings
of the software so that only the end-user experience can be tested.
 Types of White Box Testing
White box testing encompasses several testing types used to evaluate the
usability of an application, block of code or specific software package. There
are listed below —
o Unit Testing: It is often the first type of testing done on an application.
Unit Testing is performed on each unit or block of code as it is
developed. Unit Testing is essentially done by the programmer. As a
software developer, you develop a few lines of code, a single function or
an object and test it to make sure it works before continuing Unit
Testing helps identify a majority of bugs, early in the software
development lifecycle. Bugs identified in this stage are cheaper and easy
to fix.
o Testing for Memory Leaks: Memory leaks are leading causes of slower
running applications. A QA specialist who is experienced at detecting
memory leaks is essential in cases where you have a slow running
software application.
o White Box Penetration Testing: In this testing, the tester/developer has
full information of the application’s source code, detailed network
information, IP addresses involved and all server information the
application runs on. The aim is to attack the code from several angles to
expose security threats.
o White Box Mutation Testing: Mutation testing is often used to discover
the best coding techniques to use for expanding a software solution.

 Advantages of White Box Testing


o Code optimization by finding hidden errors.
o White box tests cases can be easily automated.
o Testing is more thorough as all code paths are usually covered.
o Testing can start early in SDLC even if GUI is not available.

 Disadvantages of WhiteBox Testing


o White box testing can be quite complex and expensive.

UNIT-3 Page 3
Software Testing and Project Management - 5IT5 – 12

o Developers who usually execute white box test cases detest it. The white
box testing by developers is not detailed and can lead to production
errors.
o White box testing requires professional resources with a detailed
understanding of programming and implementation.
o White-box testing is time-consuming, bigger programming applications
take the time to test fully.

 Techniques Used in White Box Testing


Data Flow Testing - Data flow testing is a group of testing strategies that
examines the control flow of programs in order to explore the sequence of
variables according to the sequence of events.
Control Flow Testing -Control flow testing determines the execution order of
statements or instructions of the program through a control structure. The
control structure of a program is used to develop a test case for the program.
In this technique, a particular part of a large program is selected by the tester
to set the testing path. Test cases represented by the control graph of the
program.
Branch Testing -Branch coverage technique is used to cover all branches of the
control flow graph. It covers all the possible outcomes (true and false) of each
condition of decision point at least once.
Statement Testing - Statement coverage technique is used to design white box
test cases. This technique involves execution of all statements of the source
code at least once. It is used to calculate the total number of executed
statements in the source code, out of total statements present in the source
code.
Decision Testing - This technique reports true and false outcomes of Boolean
expressions. Whenever there is a possibility of two or more outcomes from the
statements like do while statement, if statement and case statement (Control
flow statements), it is considered as decision point because there are two
outcomes either true or false.

UNIT-3 Page 4
Software Testing and Project Management - 5IT5 – 12

 Difference between white-box testing and black-box testing

UNIT-3 Page 5

You might also like