To generate a bug report for a given software defect or system error.

A bug is an error, flaw, or defect in software that causes it to produce an incorrect or unexpected result or behave in unintended ways.

A bug report is a formal record containing all relevant details about a detected bug. It helps developers reproduce, understand, and fix the issue efficiently.

1. To generate a bug report for a given software defect or
system error.

Prepared by:
Asst. Prof. Nikul Zinzuvadiya

2. Intro
A bug is an error, flaw, or defect in software that causes it to produce an incorrect or unexpected result or
behave in unintended ways.

A bug report is a formal record containing all relevant details about a detected bug. It helps developers
reproduce, understand, and fix the issue efficiently.
A good bug report should be clear, concise, and complete, containing:
●What went wrong
●Where and how it happened
●Steps to reproduce it
●Expected vs. actual results
Bug reports are usually managed using tools like JIRA, Bugzilla, Redmine, Trello, or GitHub Issues.

3. REQUIREMENTS:
●A sample website or software (can be your previous project)

●A text editor or spreadsheet (for manual report)

●Or any bug tracking tool like JIRA (optional)

4. PROCEDURE
1.Select a software or web application (your own project or any open-source app).

2.Test the application — explore its features and look for errors (e.g., broken button, wrong calculation, page
not loading, etc.).

3.When you find an issue, note all details:

○Page/Module where the bug occurred

○Steps to reproduce the issue

○What you expected to happen

○What actually happened

4.Document it using a standard bug report format (given below).

5.Save the report and submit it as your practical.

5. SAMPLE BUG REPORT FORMAT
Field Description
Bug ID BUG_001
Project Name Student Result Management System
Reported By [Your Name]
Date Reported 08/10/2025
Module Login Page
Severity High
Priority Medium
Environment Windows 11, Chrome Browser v128
Description Login button does not respond when valid credentials are entered.

6. Steps to
Reproduce
1. Open the login page.2. Enter valid username and password.3. Click on “Login” button.4. Nothing
happens — page remains static.
Expected ResultUser should be redirected to the dashboard after successful login.
Actual Result Page remains the same; no response or error message.
Status New
Attachment Screenshot (optional)

7. Practical Procedure
Step 1: Choose or Create a Small Project
You can use:
●A small HTML/CSS/JS website (e.g., from your previous Blisk practical).

●Or any demo project like a “Student Result Management System” or “Login Form.”
Example: Open your index.html file in a browser.

8. Step 2: Test the Application
Manually test the website or project like a user.
Look for errors such as:
●Button not working
●Wrong output
●Page not loading
●Layout distortion
●Broken links
●Form not validating inputs properly

?????? Example:
You click on the Login button after entering credentials, but nothing happens.

9. Step 3: Note Down Details of the Bug
Collect all the information needed:
●What page/module?
●What action caused it?
●What was expected?
●What actually happened?

Also, note:
●Browser name and version
●Operating system
●Date/time
Step 4: Create a Bug Report
Now write everything in a standard bug report format