How to Write a Good Bug Report: A Comprehensive Guide

1. Clear Summary:

•  Summarize the bug clearly.
•  The summary should give the bug's full picture in a single sentence.

2. One Issue = One Bug:

•  Do not combine multiple issues in one bug.
•  Because different bugs can be assigned to different developers to fix.

3. Clear & Detailed Description:

•  Expand the summary in description-simple and precise.
•  Provide as much information as possible.

4. Steps To Reproduce:

•  How can you reproduce the bug - mention it in bullet points.
•  Clear enough developers would reproduce and fix quickly.

5. Expected & Actual Results:

•  What is the requirement & what is happening?
•  The developer knows what is the issue by looking at it.

6. Additional Details As Notes:

•  Write about your additional observations.
•  Helps developers to analyze & hence fix bugs quickly.

7. Environment Details:

•  Where have you tested - QA/PRD/CHROME ETC.
•  Developer compares this with other environments.

8. Build Number:

•  In which version of the application you found the bug.

9. PRIORITY:

•  How soon the bug should be fixed.
•  Can be HIGH/LOIW/MEDIUM.

10. SEVERITY:

•  Impact on the product.
•  Can be CRITICAL/MAJOR/MINOR/TRIVIAL.

11. Screenshot/Screen Recording:

•  Evidence of the bug.
•  Can be screenshots or screen recordings.

12. Link the related test case and or story:

•  Link bug to story/test case you are testing.
•  Can be 'Associated With' OR 'Blocked By'.

13. LOGS:

•  Attach log file or snippet of log.
•  This is a mine of data for developers.

14. Avoid Duplicates:

•  Check if already bug is reported by someone. 

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

What Type of Test Cases Should Not Be Automated?

1. User Interface (UI) testing

2. Exploratory testing

3. Usability testing

4. Ad hoc testing

5. Performance testing

• Test cases that require human judgment, exploration, or unpredictability may not be suitable for automation. Additionally, test cases highly dependent on an application's user interface, performance, or usability may be better suited for manual testing.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

User Interface Test Cases: What You Need to Know

1. Navigation Test: 

• Test the navigation bar or menu by clicking on each link or button to ensure that they take you to the correct page or section of the website or application.

2. Input Validation Test: 

• Test the input fields, such as forms or search boxes, by entering valid and invalid data to ensure that the system handles the inputs correctly.

3. Button Test: 

• Test all buttons on the UI to ensure they perform the intended actions and provide appropriate feedback, such as success or error messages.

4. Compatibility Test: 

• Test the UI on different devices and browsers to ensure it is compatible with various screen sizes, resolutions, and operating systems.

5. Responsiveness Test: 

• Test the UI for responsiveness by resizing the browser window or using device emulators to see how the UI adapts to different screen sizes.

6. Content Test: 

• Test the UI for consistency and accuracy of content, including text, images, and multimedia.

7. Accessibility Test: 

• Test the UI for accessibility compliance, ensuring that users with disabilities can access and use the UI without any issues.

8. Performance Test: 

• Test the UI for performance by checking loading times, response times, and any delays or lags in the system.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

How to Send MySQL Data to an Email with Python

import smtplib
import csv
import pymysql
import json
import base64
import datetime
import smtplib
from email.mime.text import MIMEText
from email.mime.multipart import MIMEMultipart
from email.mime.application import MIMEApplication

# Connect to the MySQL database
db = pymysql.connect(host="localhost", user="root", password="pass1234", database="local")

# Execute an SQL query to retrieve data
cursor = db.cursor()
cursor.execute("SELECT * FROM local.questions")
data = cursor.fetchall()

# Write the data to a json file
data = [[str(col) if isinstance(col, datetime.datetime) else col for col in row] for row in data]
with open('data.json', 'w', encoding='utf-8', newline='') as file:
    json.dump(data, file, ensure_ascii=False)

# Open the JSON file
with open('data.json', 'r', encoding='utf-8') as file:
    data = json.load(file)

# Create the email message
from_addr = 'your@gmail.com'
to_addr = 'friend@gmail.com'
subject = 'JSON data'
msg = MIMEMultipart()
msg['From'] = from_addr
msg['To'] = to_addr
msg['Subject'] = subject

# Add the JSON file as an attachment
attachment = MIMEApplication(json.dumps(data, indent=2))
attachment['Content-Disposition'] = f'attachment; filename=data.json'
msg.attach(attachment)

# Connect to the SMTP server and send the message
server = smtplib.SMTP('smtp.gmail.com', 587)
server.starttls()
server.login(from_addr, 'Your_Gmail_APP_PASSWORD')
server.sendmail(from_addr, to_addr, msg.as_string())
server.quit()

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Bug Life Cycle In Software Testing

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.