You are on page 1of 7

GOVERNMENT POLYTECHNIC, PUNE

(An Autonomous Institute of Government of Maharashtra)

PRACTICAL NO 8
Create a defect report after executing the test cases

SUBMITTED BY:
NEHA PARSHURAM RATHOD
(1906110)

Under the Guidance of


Mrs. Reshma Chavan Mam

1
PRACTICAL NO 8
Title: Write a program and design test cases for black box testing for your
assigned project.
❖ Course Outcomes:
Create defect report for your project.
❖ Objectives:
The main objective behind performing defect report testing is to
test internal structure, design and coding of software, and to know how
efficiently our website runs.
❖ theory:
❖ Introduction:
Black box testing is a type of software testing in which the
functionality of the software is not known. The testing is done without
the internal knowledge of the products.

2
1. Syntax Driven Testing Scheme: This type of testing is applied to
systems that can be syntactically represented by some language. For
example compilers, language that can be represented by context free
grammar. In this, the test cases are generated so that each grammar is
used at least once.
2.Equivalence partitioning – It is often seen that many types of inputs
work similarly so instead of giving all of them separately we can group
them together and test only one input of each group. The idea is to
partition the input domain of the system into a number of equivalence
classes such that each member of class works in a similar way, i.e., if a
test case in one class results in some error, other members of class would
also result into same error.
The technique involves two steps:
1. Identification of equivalence class – Partition any input domain into
minimum two sets: valid values and invalid values. For example, if the
valid range is 0 to 100 then select one valid input like 49 and one invalid
like 104.
2. Generating test cases – (I) To each valid and invalid class of input
assign unique identification number.
(ii) Write test case covering all valid and invalid test case considering that
no two invalid inputs mask each other.
To calculate the square root of a number, the equivalence classes will be:
(a) Valid inputs:
• Whole number which is a perfect square- output will be an integer.

3
• Whole number which is not a perfect square- output will be decimal
number.
• Positive decimals
1. (b) Invalid inputs:
• Negative numbers (integer or decimal).
• Characters other that numbers like “a”,”!”,”;”, etc.
2. Boundary value analysis – Boundaries are very good places for errors
to occur. Hence if test cases are designed for boundary values of input
domain, then the efficiency of testing improves and probability of finding
errors also increase. For example – If valid range is 10 to 100 then test for
10,100 also apart from valid and invalid inputs.

3. Cause effect Graphing – This technique establishes relationship


between logical input called causes with corresponding actions called
effect. The causes and effects are represented using Boolean graphs. The
following steps are followed:
1. Identify inputs (causes) and outputs (effect).
2. Develop cause effect graph.
3. Transform the graph into decision table.
4. Convert decision table rules to test cases.

Advantages and Disadvantages


Advantages

4
• The tester does not need to have a technical background. It is
important to test by being in the user’s shoes and think from the
user’s point of view.
• Testing can start once the development of the project/application is
done. Both the testers and developers work independently without
interfering in each other’s space.
• It is more effective for large and complex applications.
• Defects and inconsistencies can be identified in the early stages of
testing.
Disadvantages
• Without any technical or programming knowledge, there are
chances of ignoring possible conditions of the scenario to be tested.
• In a stipulated time, there is a possibility of testing less and skipping
all possible inputs and their output testing.
• Complete Test Coverage is not possible for large and complex
projects.

CASE STUDY:
❖ Two invalid classes will be:
The email and password will both be incorrect. either one of them
will be incorrect and both of them will be correct.

5
testing Report:
Test no Test step Test data ExpectedActual status
result result
1 Enter Email= Login inRedirectin
email password g to the fail
same page
2 Enter Email= Option for Option for pass
password password sign up sign up

we found out the actual reason behind the error that our project was
giving it was due to the error of the linking that we have done in the
coding of the project. Due to the defect report testing we have come to
know the actual error in our project. After the correction the table
somehow look like this,

6
Test no Test steps Test data Expected Actual status
result result
1 Enter Email=pas Login in Login in pass
email sword
2 Enter Email= Option for Option for pass
password password sign up sign up

CONCLUSION:
These are some of the basic points regarding defect report testing and
the overview of its
techniques and methods. As it is not possible to test everything with
human involvement with 100 percent accuracy, if the above-mentioned
techniques and methods are used effectively, then it will definitely
improve the quality of the system. To conclude, this is a very helpful
method to verify the functionality of the system and identify most of the
defects.

REFERENCES
1. https://www.xenonstack.com/insights/what-is-white-box-testing
2. https://www.guru99.com/white-box-testing.html
3. https://www.tutorialspoint.com/software_testing_dictionary
4. https://en.wikipedia.org/wiki/White_box_(software_engineering)

You might also like