Black box testing

Black box testing is a technique of software testing

which examines the functionality of software without
peering into its internal structure or coding. The
primary source of black box testing is a specification
of requirements that is stated by the customer.
Generic steps of black box testing
The black box test is based on the specification of requirements, so it is
examined in the beginning.
 In the second step, the tester creates a positive test scenario and an
adverse test scenario by selecting valid and invalid input values to check
that the software is processing the correctly or incorrectly.
In the third step, the tester develops various test cases such as decision
table, all pairs test, equivalent division, error estimation, cause-effect
graph, etc
The fourth phase includes the execution of all test cases.
In the fifth step, the tester compares the expected output against the
actual output.
In the sixth and final step, if there is any flaw in the software,
then it is cured and tested again.
 Test procedure
• The test procedure of black box testing is a kind of
process in which the tester has specific knowledge about
the software's work, and it develops test cases to check
the accuracy of the software's functionality.
• It does not require programming knowledge of the
software. All test cases are designed by considering the
input and output of a particular function
• here are various techniques used in black box testing for
testing like decision table technique, boundary value
analysis technique, state transition, All-pair testing,
cause-effect graph technique, equivalence partitioning
technique, error guessing technique, use case technique
and user story technique.
 Test procedure
• Test cases are created considering the
specification of the requirements. These test
cases are generally created from working
descriptions of the software including
requirements, design parameters, and other
specifications.
 Techniques Used in Black Box Testing

• Decision table technique-Decision Table Technique is a systematic approach where various

input combinations and their respective system behavior are captured in a tabular form. It
is appropriate for the functions that have a logical relationship between two and more
than two inputs.
• Boundary value Technique-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.
• All pair Testing technique-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.
• Use case technique-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.
• Error guessing technique-Error guessing is a technique in which there is no specific method
for identifying the error. It is based on the experience of the test analyst, where the tester
uses the experience to guess the problematic areas of the software.
 SDLC(software development life cycle)
• A software life cycle model (also termed
process model) is a pictorial and diagrammatic
representation of the software life cycle. A life
cycle model represents all the methods
required to make a software product transit
through its life cycle stages. It also captures
the structure in which these methods are to
be undertaken.
 Need of SDLC

• The development team must determine a suitable life

cycle model for a particular plan and then observe to it.
• Without using an exact life cycle model, the development
of a software product would not be in a systematic and
disciplined manner. When a team is developing a software
product, there must be a clear understanding among team
representative about when and what to do. Otherwise, it
would point to chaos and project failure. This problem can
be defined by using an example. Suppose a software
development issue is divided into various parts and the
parts are assigned to the team members.
Sdlc cycle
 The stages of SDLC are as follows

• Stage1: Planning and requirement analysis

• Requirement Analysis is the most important and necessary stage
in SDLC.
• The senior members of the team perform it with inputs from all
the stakeholders and domain experts or SMEs in the industry.
• Planning for the quality assurance requirements and
identifications of the risks associated with the projects is also
done at this stage.
• For Example, A client wants to have an application which
concerns money transactions. In this method, the requirement
has to be precise like what kind of operations will be done, how
it will be done, in which currency it will be done, etc.
 Stage2: Defining Requirements
• Once the requirement analysis is done, the
next stage is to certainly represent and
document the software requirements and get
them accepted from the project stakeholders.
• This is accomplished through "SRS"- Software
Requirement Specification document which
contains all the product requirements to be
constructed and developed during the project
life cycle.
 Stage3: Designing the Software
The next phase is about to bring down all the knowledge of
requirements, analysis, and design of the software project. This phase
is the product of the last two, like inputs from the customer and
requirement gathering
Stage4: Developing the project
In this phase of SDLC, the actual development begins, and the
programming is built. The implementation of design begins concerning
writing code. Developers have to follow the coding guidelines
described by their management and programming tools like compilers,
interpreters, debuggers, etc. are used to develop and implement the
code.
 Stage5: Testing
• After the code is generated, it is tested against
the requirements to make sure that the
products are solving the needs addressed and
gathered during the requirements stage.
• During this stage, unit testing, integration
testing, system testing, acceptance testing are
done.
 Stage6: Deployment
• Once the software is certified, and no bugs or
errors are stated, then it is deployed.
• Then based on the assessment, the software
may be released as it is or with suggested
enhancement in the object segment.
• After the software is deployed, then its
maintenance begins.
 Stage7: Maintenance
Once when the client starts using the developed systems, then the
real issues come up and requirements to be solved from time to
time.
This procedure where the care is taken for the developed product
is known as maintenance.
 V model
V-Model also referred to as the Verification
and Validation Model. In this, each phase of
SDLC must complete before the next phase
starts. It follows a sequential design process
same as the waterfall model. Testing of the
device is planned in parallel with a
corresponding stage of development.