Sample Bug Report

The Sample, Bug/Defect Report given below will give you an exact idea of how to report a Bug in the Bug Tracking Tool?

Here is an Example scenario that caused a Bug:

Let’s assume that in your application under test you want to create a new user with user information, for that you need to login into the application and navigate to the USERS menu -> New User, then enter all the details in the ‘User form’ like, First Name, Last Name, Age, Address, Phone etc.

Once you enter all this information, you need to click on the ‘SAVE’ button in order to save the user. Now you can see a successful message saying, “New User has been created successfully”.

But when you entered into your application by logging in and you have navigated to the USERS menu -> New user, entered all the required information to create the new user and clicked on SAVE button.

Sample bug report

BANG! The application crashed and you got one error page on the screen. (Capture this error message window and save it as a Microsoft paint file)

Now, this is a Bug scenario and you would like to report this as a BUG in your Bug-Tracking Tool.

How Will You Report This Bug Effectively?

Sample Bug Report

Here is a sample Bug Report for the above-mentioned example:
(Note that some ‘Bug Report’ fields might differ depending on your bug tracking system)


Bug Name: Application crashes upon clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug).
Area Path: USERS menu -> New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005

Description: Application crashes upon clicking the SAVE button while creating a new the user, hence unable to create a new user in the application.

Steps to Reproduce:

1) Login into the Application.
2) Navigate to the Users Menu -> New User
3) Filled out all the user information fields.
4) Clicked on the ‘Save’ button.
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information (Attach more logs related to the bug..IF any)
7) Also see the attached screenshot of the error page.

Expected Result: On clicking the SAVE button, you should be prompted to a successful message “New User has been created successfully”.

(Attach ‘application crash’ screenshot. IF any)

Save the Defect/Bug in the BUG TRACKING TOOL.  You will get a Bug ID that you can use for further bug reference.

Default ‘New Bug’ mail will go to the respective developer and the default module owner (Team leader or manager) for further action.

If you need more information about writing a Good Bug Report, read our previous post “How to write a Good Bug Report“.

Recommended Reading

174 thoughts on “Sample Bug Report”

  1. hello everyone i want test cases plan for defect tracking and bug fixing system project , if anyone knows tell me…..

    • software testing life cycle is the procedure to test software.
      In the software testing life cycle, there are many phases like,
      1-Requirements analysis: Requirement analysis refers to the step where the Software Testing Lifecycle begins, In requirement analysis, we analyze the requirement means how to test, whom to test and in this phase, we gather the requirements
      2-Test planning: During this phase, the test strategy is outlined in a test plan document. This strategy includes tools needed, testing steps, and roles and responsibilities. Part of determining this strategy is a risk and cost analysis and an estimated timeline for testing.
      3-Test environment setup: During this phase, testing environments are configured and deployed. This phase may include a variety of testing tools, including TestComplete, Selenium, Appium, or Katalon Studio. Sometimes, this phase also includes setting up test servers. Once environments are deployed, smoke tests are performed to ensure that environments are working as expected with all intended functionality.
      4-Test execution: During this phase, features are tested in the deployed environment, using the established test cases. Expected test results are compared to actual and results are gathered to report back to development teams.
      5- Test closure: This is the last phase of the STLC, during which a test result report is prepared. This report should summarize the entire testing process and provide comparisons between expected results and actual. These comparisons include objectives met, time taken, total costs, test coverage, and any defects found.

  2. Hi Vijay Sir,

    Thank you so much for updating such crispy knowledge
    on this web site. i am avid reader for your article past one year .

  3. Hello,
    Good artical on bug report.
    How can QA report bug to dev if he/she has a video file(.swf,mp4)?
    sometimes screenshot is not enought to explain bug,I have record screen using jing.
    but how to send it to dev??(Except email)
    Is there any bug tracking tool??

    • hii,
      You can use awesome screenshot as well,where you can take the screenshot along with the video recording option as well..And when ever you will record video or take screenshot so the app will create a link for that particular bug and even you can use that link in excel and can easily send the url at any environment e.g-excels,mails,whatsapp etc

  4. My Doubt is Built-in Exceptions like ArrayIndexOutOfBoundException,NullPointerException etc displayed while we are testing(Manually) a web application should be considered as bugs or not.If we Consider them as bugs what priority and severity must be given to that bug.

    Pls Can anyone answer?

  5. You have 19 advertisements on this ONE page! Holy crap. This is absolutely sickening. Guys C’mon! Good Content but Jesus.

    • @rana
      You can check this

  6. hi
    I am Nisha.
    I need to see a standard terminology of Bug Report which is mostly used in IT/Computer firms nowadays.
    Please, can you provide me?

    • Test Case is the small part of test scenario. Test case confirm that each module and each actions are working properly or not in low level testing. Whereas, Test scenario is the process of testing collection of test cases in a bulk. Test Scenario confirms that, product is working as per end users requirements or not as a whole as per their need.

  7. Incredible update of captcha solution software “XEvil 5.0”:

    Captchas breaking of Google (ReCaptcha-2 and ReCaptcha-3), Facebook, BitFinex, Bing, Hotmail, SolveMedia, Yandex,
    and more than 12000 another size-types of captchas,
    with highest precision (80..100%) and highest speed (100 img per second).
    You can use XEvil 5.0 with any most popular SEO/SMM software: iMacros, XRumer, SERP Parser, GSA SER, RankerX, ZennoPoster, Scrapebox, Senuke, FaucetCollector and more than 100 of other programms.

    Interested? There are a lot of impessive videos about XEvil in YouTube.


    See you later!


Leave a Comment