December 1, 2023

In the world of software development, defects or bugs can occur despite thorough testing and quality assurance measures. These defects can lead to issues and hinder the smooth functioning of software applications. Therefore, it is crucial for users, testers, and stakeholders to effectively report defects to ensure their timely resolution. In this blog post, We will guide you through the process of How to Report a Defect, covering important aspects such as defect title, test environment, description, test steps, expected result, actual result, assignee, priority and severity, labels, and other necessary points.

Defect/ Bug Title:

When reporting a defect, it is essential to provide a clear and concise title that accurately represents the issue. The title should be descriptive enough to help others understand the problem at a glance. For example, instead of using a vague title like “Error in Application,” a more specific title such as “Login Page Fails to Load on Safari Browser” provides better clarity.

Test Environment or Precondition:

To reproduce the defect and facilitate its resolution, it is important to mention the test environment or preconditions under which the issue occurred. This includes details such as the operating system, browser version, device type, network conditions, or any specific configuration required. Providing this information helps developers replicate the issue and understand its context.


How to Report a Defect? The defect description should provide a comprehensive overview of the problem. It should include relevant details such as the exact steps taken to encounter the defect, any error messages or pop-ups received, and the impact on the system or user experience. A well-written description helps the developers understand the issue and its implications clearly.

Test Steps:

To ensure that the defect can be reproduced, it is crucial to provide a step-by-step guide outlining the actions taken before encountering the problem. This helps developers follow the same sequence of actions and observe the issue firsthand. Including screenshots or video, recordings can also be beneficial in providing additional visual context.

Expected Result:

Clearly state what you expected the system to do in response to the given test steps. This describes the intended behavior or outcome. For example, “Clicking on the submit button should save the form and display a success message.”

Actual Result:

Describe the actual behavior observed during testing. This explains how the system actually behaved, deviating from the expected result. For example, “Clicking on the submit button does nothing and no success message is displayed.”


Specify the individual or team responsible for addressing the defect. This could be a developer, a tester, or a specific department within the organization. Assigning the defect to the appropriate person or team streamlines the resolution process and ensures accountability.

Priority and Severity:

Assigning a priority and severity level to the defect helps prioritize its resolution. Priority determines the urgency of fixing the issue, while severity defines the impact of the defect on the system or users. Common priority levels include high, medium, and low, while severity levels can range from critical to minor. Properly categorizing the defect enables efficient resource allocation and ensures critical issues are addressed promptly.


Labels or tags are used to classify defects based on their nature, functional area, or any other relevant criteria. These labels help in organizing and tracking defects more effectively. For example, you can use labels like “UI”, “Performance”, “Security”, “Functional”, or any other relevant categories to categorize the defects.


How to Report a Defect? Reporting defects is a vital part of the software development lifecycle. By following the guidelines outlined in this blog post, you can effectively report defects, enabling developers to understand, reproduce, and resolve issues efficiently. Remember, the quality of defect reporting plays a significant role in ensuring smooth software operation and delivering an exceptional user experience.

Let’s Take The Example Of Facebook – How to Report a Defect:

Here Is a sample example of a defect in that front-end validation is not enabled on the login page of Facebook at the username and password field. It is also accepting a blank username and blank password instead of that it should give an error message that the username and password cannot be blank.

Front End Validation Missing on Facebook Login Page for Username and Password Fields- How to Report a Defect:


Browser: Google Chrome (Version 93.0.4577.82)
Build/Commit Details: Facebook Login Page Version 2.1.0
PHP Version: 7.4.9
MySQL Version: 8.0.21


The login page on Facebook is experiencing a defect where front-end validation is not being enforced for the username and password fields. As a result, users can submit the login form with blank username and password fields, which should not be allowed. The expected behavior is for the system to display an error message indicating that both the username and password fields cannot be blank.

Test Steps:

Launch the Google Chrome browser.
Navigate to the Facebook login page.
Leave the username field blank.
Leave the password field blank.
Click the “Log In” button.

Expected Result:

The system should display an error message indicating that both the username and password fields cannot be blank. The user should not be able to proceed with the login process until valid inputs are provided.

Actual Result:

The system accepts the blank username and password fields without displaying any error message. The login process proceeds, potentially resulting in unauthorized access or undesired behavior.

Assignee: Development Team

Priority: High
Severity: Major

Labels: Front-end, Validation, log in, Security

Additional Information:

Date and Time of Occurrence: June 22, 2023, 10:30 AM UTC
Associated Reference Number: FB-1234


By following the provided defect reporting format, we have described an issue with the front-end validation on the Facebook login page. This defect allows users to submit the login form with blank username and password fields, instead of displaying an error message. Reporting such defects with accurate details helps developers identify and address the issue promptly, ensuring the security and functionality of the application.

Visit Website

Contact US





Leave a Reply

Your email address will not be published. Required fields are marked *