DEPARTMENT OF COMPUTER ENGINEERING

Subject: Software Testing Subject Code:22516

Semester: 05 Course: CO5I-B
Laboratory No: L003C Subject Teacher: Prof. Vijayalaxmi Kondal
Name of Student: Anushree Chorghe Roll ID:22203B0026

Experiment No: 10
Title of Experiment Generate Defect report for Library Management System.

Defect Report for Online Library Management System

Date: October 5,2023

Reported By: XYZ

Summary:- Unable to add a new book to the library inventory

Description: When attempting to add a new book to the library inventory through the “Add
Book” Functionality, the system displays an error message and does not save the book
information. The issues is consistent and reproducible all browsers and devices.

Steps to Reproduce:-
1.Log in to the library management system.
2. Nevigate to the “Add Book” Section.
3.Fill Out the required book details
4. Click the “Save” button

Expected Results:- The book information should be saved successfully ,and the system should
display a confirmation message indicating that the book has been added to the inventory.

Actual Result:- An error message is displayed, stating: “Error: Unable to save book information.
Please try again”

Saverity:- Major
Priority:- High

Environment:-
Opearting System:- Window 10
Browser:- Google Chrome Version 94.0.4606.61(64-bit)

Attachments:- N/A

Status:- New

Assigened To:- Development Team

Comments :- This defect Prevents the addition of new books to the library inventory ,impacting
the functionality of the system . Further investigating is needed to idenify the root cause and
implement a fix.

Recommednation/Resolution:- Inspect the “Add Book” functionality to idenify the cases of the
error and implement the necessary changes to allow successful book addition.

Deadline:- October 10,2023

Approaval :[To be filled by managemnet or QA]

Practical Related Questions

1.Compare Defect, Error and failure

Defect Error Failure

The Defect is the An Error is a mistake made in If the software has lots of
difference between the actual the code; that's why we cannot defects, it leads to failure or
outcomes and expected execute or compile causes failure
outputs code.
The Testers identify the The Developers and automation The failure finds by the manual
defect. And it was also solved test engineers raise the error test engineer through the
by the development cycle.
developer in the
development phase or stage
Different type of Different type of Error is as ---------
Defects are as follows: Based below:
on priority:-  Syntactic Error
 High  User interface error
 Medium  Flow control error
 Low  Error handling error
And based on the severity:  Calculation error
 Critical  Hardware error
 Major  Testing Error
 Minor
 Trivial
With the help of Below are ways The way to
the following, we to prevent prevent failure are as follows:
can prevent the Errors:
the Defects: Confirm re-testing.
Enhance the
Implementing software quality Review the
with system requirements and
several innovative
review and revisit the
programming methods.
programming. specifications.
 Use of primary and Detect the issues Implement
correct software and prepare a suitable current protective
development mitigation plan. techniques.
techniques.
Validate the fixes and verify
their quality and Categorize and evaluate errors
Peer review It is executing precision. and issues.
consistent code
reviews to evaluate
its quality and
correctness.

Describe different status of Defects.

Ans:-
 New: When a new defect is logged and posted for the first time. It is assigned a status as
NEW.
 Assigned: Once the bug is posted by the tester, the lead of the tester approves the bug
and assigns the bug to the developer team
 Open: The developer starts analyzing and works on the defect fix Fixed: When a
developer makes a necessary code change and verifies the change, he or she can make
bug status as "Fixed."
 Pending retest: Once the defect is fixed the developer gives a particular code for
retesting the code to the tester. Since the software testing remains pending from the
testers end, the status assigned is "pending retest."
 Verified: The tester re-tests the bug after it got fixed by the developer. If there is no bug
detected in the software, then the bug is fixed and the status assigned is "verified."
 Reopen: If the bug persists even after the developer has fixed the bug, the tester changes
the status to "reopened". Once again the bug goes through the life cycle.
 Closed: If the bug is no longer exists then tester assigns the status "Closed."
 Duplicate: If the defect is repeated twice or the defect corresponds to the same concept
of the bug, the status is changed to "duplicate."
 Rejected: If the developer feels the defect is not a genuine defect then it changes the
defect to "rejected."
 Deferred: If the present bug is not of a prime priority and if it is expected to get fixed in
the next release, then status "Deferred" is assigned to such bugs
 Not a bug: If it does not affect the functionality of the application then the status
assigned to a bug is "Not a bug"
3. Describe various defects reporting process with example.
Ans:-

Defect reporting process in Medium Scale Organization is:

TESTER

TEST HEAD

DEVELOPMENT HEAD

DEVELOPER

Defect reporting process in Large Scale Organization is:

TESTER

TEST HEAD

DEFECT TRACKING TOOL

DEVELOPMENT HEAD

DEVELOPER
Exercise
1.Generate online library management system with the help of following website. Perform
at least 4 tests for same. Prepare defect report for library management system.
• https://librarika.com/
Sr.No Test Test Case Input Expected Actual Status
Case Id description Data Results Results
1 TC-1 User Valid User should User Pass
Registration user be registered
details registered
successfully
2 TC-2 Search Book Book Book Book Pass
by Title Title: details for found
"The "The Great
Great Gatsby"
Gatsby" should
appear
3 TC-3 Borrow Book Book ID: Book Book Pass
12345, should be borrowed
User ID: marked as
67890 borrowed
by user
4 TC-4 Return Book Book ID: Book Book Pass
12345, should be returned
User ID: marked as
67890 available

Defect Report for Online Library Management System

Date: October 5,2023

Reported By: XYZ

Summary:- Unable to add a new book to the library inventory

Description: When attempting to add a new book to the library inventory through the “Add
Book” Functionality, the system displays an error message and does not save the book
information. The issues is consistent and reproducible all browsers and devices.

Steps to Reproduce:-
1.Log in to the library management system.
2. Nevigate to the “Add Book” Section.
3.Fill Out the required book details
4. Click the “Save” button

Expected Results:- The book information should be saved successfully ,and the system should
display a confirmation message indicating that the book has been added to the inventory.

Actual Result:- An error message is displayed, stating: “Error: Unable to save book information.
Please try again”

Saverity:- Major

Priority:- High

Environment:-
Opearting System:- Window 10
Browser:- Google Chrome Version 94.0.4606.61(64-bit)

Attachments:- N/A

Status:- New

Assigened To:- Development Team

Comments :- This defect Prevents the addition of new books to the library inventory ,impacting
the functionality of the system . Further investigating is needed to idenify the root cause and
implement a fix.

Recommednation/Resolution:- Inspect the “Add Book” functionality to idenify the cases of the
error and implement the necessary changes to allow successful book addition.

Deadline:- October 10,2023

Approaval :[To be filled by managemnet or QA

 Marks Obtained Dated signature of Teacher

ProcessRelate Product Related Total

d (15) (50)
(35)