πŸ“Œ Steps to Log a Bug in Manual Testing

Step 1: Find the Bug

πŸ‘‰ Test the software manually and identify a problem (e.g., clicking a button does nothing).

Step 2: Reproduce the Bug

πŸ‘‰ Try repeating the same steps to confirm that the issue happens consistently.

Step 3: Capture Details

πŸ‘‰ Take screenshots or videos to show what’s wrong.

Step 4: Log the Bug in a Bug Tracking Tool

πŸ‘‰ Open a bug tracking tool (like JIRA, Bugzilla, or Trello) and fill in the details:

  • Bug ID: A unique number assigned to the bug.
  • Title: A short description of the issue (e.g., “Submit button not working”).
  • Description: Step-by-step details to reproduce the bug.
  • Severity & Priority: How serious the bug is (e.g., Critical, High, Medium, Low).
  • Expected Result: What should happen.
  • Actual Result: What actually happens.
  • Attachments: Screenshots/videos.

Step 5: Assign & Track the Bug

πŸ‘‰ The bug is assigned to a developer for fixing. After fixing it, the tester rechecks it to ensure it’s resolved.


πŸ“Š Easy-to-Understand Diagram

mathematicaCopyEdit   πŸ” Find Bug  
        ↓  
   πŸ” Reproduce Bug  
        ↓  
   πŸ“Έ Capture Details (Screenshots)  
        ↓  
   πŸ“ Log Bug in Tracking Tool  
        ↓  
   πŸ“’ Assign to Developer  
        ↓  
   βœ… Recheck After Fix  

Example of a Bug Report

FieldDetails
Bug ID (E.g. TC_001) with identification no: TC_001
TitleSteps to Reproduce:
1. Go to the checkout page
2. Fill in payment details
3. Click the “Submit” button
Expected Result: Payment should process
Actual Result: The button does nothing
DescriptionSteps to Reproduce:
1. Go to the checkout page
2. Fill in payment details
3. Click the “Submit” button
Expected Result: Payment should process
Actual Result: Button does nothing
SeverityHigh
PriorityCritical
AttachmentsScreenshot of the issue
Assigned ToRaphael Wong

Why Is Proper Bug Logging Important?

πŸ“Œ Helps developers fix issues faster
πŸ“Œ Prevents the same bug from happening again
πŸ“Œ Improves software qualit

How to Log a Bug in Google Spreadsheet (Manual Testing)?

If you don’t have a bug-tracking tool like JIRA or Bugzilla, you can use Google Spreadsheet to log and track bugs in manual testing.


πŸ“Œ Steps to Log a Bug in Google Spreadsheet

Step 1: Create a Google Spreadsheet

πŸ‘‰ Open Google Sheets and create a new sheet named “Bug Tracker”.

Step 2: Add Column Headers

πŸ‘‰ Set up the following columns:

Bug IDTitleDescriptionSteps to ReproduceExpected ResultActual ResultSeverityPriorityStatusAssigned ToDate FoundAttachments

Step 3: Find and Reproduce the Bug

πŸ‘‰ Test the software manually, find a bug, and check if it happens repeatedly.

Step 4: Enter Bug Details in the Spreadsheet

πŸ‘‰ Fill in the details in the respective columns.

Step 5: Assign the Bug and Track the Status

πŸ‘‰ Assign the bug to a developer and update the Status column (e.g., Open, In Progress, Fixed, Retested, Closed).


πŸ“Š Easy-to-Understand Diagram

mathematicaCopyEdit   πŸ” Find Bug  
        ↓  
   πŸ” Reproduce Bug  
        ↓  
   πŸ“ Log in Google Spreadsheet  
        ↓  
   πŸ“’ Assign to Developer  
        ↓  
   βœ… Update Status After Fix  

Example of a Bug Report in Google Spreadsheet


Bug IDTitleDescriptionSteps to ReproduceExpected ResultActual ResultSeverityPriorityStatusAssigned ToDate FoundAttachments
TC- 101Login button not workingUser unable to log in1. Go to login page
2. Enter valid credentials
3. Click “Login”
User should log inNothing happensHighCriticalOpenDev Team2025-02-13Screenshot.png
TC_102Checkout page crashesPayment page does not load1. Add items to cart
2. Click “Checkout”
Payment should be processedPage crashesCriticalHighIn ProgressDev Team2025-02-13Error_log.txt

Why Use Google Spreadsheet for Bug Tracking?

βœ… Easy to use – No need for complex tools
βœ… Collaborative – Multiple testers can update in real-time
βœ… Free & Accessible – Works anywhere with an internet connection
βœ… Customizable – Can add more columns like Bug Type, Browser, OS

Using Google Spreadsheet makes bug tracking simple and efficient, helping teams fix issues faster and more effectively!

Leave a comment