Scribd
Upload
15 views7 pages

Black Box Testing

Uploaded by

Sadia Awan
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
15 views7 pages

Black Box Testing

Uploaded by

Sadia Awan
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/ 7

Black Box testing:

Black Box Testing is a software testing method in which the functionalities of software
applications are tested without having knowledge of internal code structure, implementation
details and internal paths. Black Box Testing mainly focuses on input and output of software
applications, and it is entirely based on software requirements and specifications.
For Example, an operating system like Windows, a website like Google, a database like Oracle
or even your own custom application. Under Black Box Testing, you can test these applications
by just focusing on the inputs and outputs without knowing their internal code implementation.
Various parameters checked in black box testing are:
 Accurate actions performed by users
 System’s interaction with the inputs
 The response time of the system
 Use of data structures Issues in the user interface
 Usability issues
 Performance issues
Types of Black Box Testing
There are many different types of Black Box Testing, some of them are given below:
 Functional testing – This is a type of black box testing which is related
to the functional requirements of a system; Functional testing is
concerned only with the functional requirements of a system and covers
how well the system executes its functions.
 Non-functional testing – This black box testing type is not related to
testing of specific functionality, Non functional testing is concerned with
the non-functional requirements and is designed specifically to evaluate
the readiness of a system according to the various criteria which are not
covered by functional testing.
 Regression testing – Regression Testing is performed after code fixes,
upgrades or any other system maintenance to check the new changes has
not affected any existing functionality.
How to do BlackBox Testing
Here are the generic steps followed to carry out any type of Black Box Testing.
 Initially, the requirements and specifications of the system are examined.
 Tester chooses valid inputs (positive test scenario) to check whether SUT processes them
correctly. Also, some invalid inputs (negative test scenario) are chosen to verify that the
SUT is able to detect them.
 Tester determines expected outputs for all those inputs.
 Software tester constructs test cases with the selected inputs.
 The test cases are executed.
 Software tester compares the actual outputs with the expected outputs.
 Defects if any are fixed and re-tested.

Tools used for Black Box Testing:


Tools used for Black box testing largely depends on the type of black box testing you
are doing.
 For Functional/ Regression Tests you can use – QTP, Selenium
 For Non-Functional Tests, you can use – LoadRunner, Jmeter

What are Black Box testing techniques?


There are various test case design techniques applied for black-box testing:
1. Boundary Value Analysis
2. Equivalence partitioning
3. State Transition Testing
4. Decision Table Testing
5. Graph-Based Testing
6. Error Guessing Technique

Boundary value analysis


Boundary value analysis is a technique to test boundary value between valid and invalid
partitions in test case design. For the most part, errors are observed in the extreme ends of the
input values, so these extreme values like start/end or lower/upper values are called Boundary
values and analysis of these Boundary values is called “Boundary Value Analysis”. It is also
sometimes known as ‘Range Checking’.
Boundary value analysis is another black box test design technique and it is used to find the
errors at boundaries of input domain rather than finding those errors in the center of input.

From the above table, we can view the following inputs that are given.
 The minimum boundary value is given as 21.
 The maximum boundary value is given as 65.
 The valid inputs for testing purposes are 21, 22, 64 and 65.
 The invalid inputs for test cases are 20 and 66.
Test Case Scenarios
1. Input: Enter the value of age as 20 (21-1)
Output: Invalid
2. Input: Enter the value of age as 21
Output: Valid
3. Input: Enter the value of age as 22 (21+1)
Output: Valid
4. Input: Enter the value of age as 65
Output: Valid
5. Input: Enter the value of age as 64 (65-1)
Output: Valid
6. Input: Enter the value of age as 66 (65+1)

Output: Invalid

From the above table, we can view the following inputs that are given.
 The minimum boundary value is given as 8.
 The maximum boundary value is given as 14.
 The valid character lengths for testing purpose are 8, 9, 14 and 13
 The invalid character lengths for test cases are 7 and 15.
Test Case Scenarios
1. Input: Enter the text length as 7 (Min length -1)
Output: Invalid
2. Input: Enter the text length as 8 (Min length)
Output: Valid
3. Input: Enter the text length as 9 (Min length +1)
Output: Valid
4. Input: Enter the text length as 14 (Max length)
Output: Valid
5. Input: Enter the value of age as 13 (Max length -1)
Output: Valid
6. Input: Enter the value of age as 15 (Max length +1)
Output: Invalid

Equivalence Class Partitioning:


Dividing the test input data into a range of values and selecting one input value from each range
is called Equivalence Partitioning. It is applied when the need for exhaustive testing arises and
for resisting the redundancy of inputs.
Guidelines for Equivalence Partitioning :
 If the range condition is given as an input, then one valid and two invalid
equivalence classes are defined.
 If a specific value is given as input, then one valid and two invalid
equivalence classes are defined.
 If a member of set is given as an input, then one valid and one invalid
equivalence class is defined.
 If Boolean no. is given as an input condition, then one valid and one invalid
equivalence class is defined.
Types of Equivalence Class Testing
The equivalence class testing is divided into four different types that forms an integral part of
testing mechanisms and perform action based on different data sets.
They are as follows:
Weak Normal Testing Class: This type of testing uses only a single variable from each
equivalence class during test cases. The word weak signifies single fault and in the testing
scenario, there is only one element. The tester identifies the values in a systematic way.
Strong Normal Testing Class: This type of testing is associated with multiple fault assumptions
and test cases are required for each element from equivalence class and the testing team covers
the whole equivalence class by using every possible inputs.
Weak Robust Testing Class: This type of testing results into single fault as it is weak and the
expected output from invalid test cases cannot be defined. The testers usually spend a huge
amount of time for defining the expected output from the test cases. The testing team mainly
focus on testing the test cases for invalid values.
Strong Robust Testing Class: This form of class testing is redundant. So multiple fault
assumptions are present and the equivalence classes are measured in the terms of valid and
invalid inputs from test cases. However, for the testing team it is not feasible for reducing the
redundancy.
Example-1:
Let us consider an example of any college admission process. There is a college that
gives admissions to students based upon their percentage.
Consider percentage field that will accept percentage only between 50 to 90 %, more
and even less than not be accepted, and application will redirect user to an error page. If
percentage entered by user is less than 50 %or more than 90 %, that equivalence
partitioning method will show an invalid percentage. If percentage entered is between
50 to 90 %, then equivalence partitioning method will show valid percentage.

Example-2 :
Let us consider an example of software application. There is function of software
application that accepts only particular number of digits, not even greater or less than
that particular number.
Consider an OTP number that contains only 6 digit number, greater and even less than
six digits will not be accepted, and the application will redirect customer or user to error
page. If password entered by user is less or more than six characters, that equivalence
partitioning method will show an invalid OTP. If password entered is exactly six
characters, then equivalence partitioning method will show valid

You might also like