How to write a test report?

Hey Guys! If you are a newbie in the field of software testing and don't know how to write a test report, then you are in the right place. In this article, a brief and simple explanation will give you a full hold on the test report. Writing an effective test report is a vital part of software testing.

When you send a bug to the Project Manager for checking, then the project manager will verify the bug easily if your test report has written simply and descriptively. On the other way, the Project Manager will send it back for more explanation. Now let's see what is the structure of a well-written test report and What are the fundamental elements of a test report?

Structure of the Test Report

The following are the fundamental elements of a test report. Now let's go in more detail and try to understand what about they are?

1. Environment
2. Browser
3. Desktop/Device
4. Title of Bug
5. Testing Details
6. Images
7. Testing URLs
8. Status
9. CC (Participants)
10. Notes (Optional Part)

Environment: Environment section describes the operating system which you are using to test a bug. If you are using Windows/Ubuntu or any other you can write it in the environment section.

Browser: In this section, you can write the name of browsers you are using for testing. Like Chrome, Firefox, IE, Opera, and Safari.

Desktop/Device: Here you can mention the name of devices that you are using to test a bug. If you are testing on Desktop then you can write "Desktop" if you are testing on Mobile Phones you can write the names of devices like iPhone 6/7/8, Huawei y7 prime, etc.

Title of Bug: Write the title of the bug that you have tested.

Testing Details: This section contains the testing details that you have tested. You should write all the points to clarify what you have tested. Normally points are written in the form of Test Cases. Write all the possible scenarios here so that the Project Manager could get understanding that you have covered all the things. It should be more descriptive.

Images: In this section, images are attached to the test report. Image's attachment is necessary because they will show that things are working fine practically. With the help of images, PM can easily see the corrected things. Without executing the application he can confirm that bug is fixed now.

Testing URLs: In this section, write the URLs that have used for testing.

Status: Status will be Fail or Pass.

CC (Participants): In this section, we tag the participants like Project Manager and Business Guys so that they could get intimated when you attach the test report.

Sample Test Report:

Environment:  Ubuntu 18

Browser: Chrome, Firefox, etc

Desktop/Devices: Desktop

Title:

Login Page - Sign in functionality is not working.

Testing Details:

Test Case1: Sign-in is working fine with valid credentials
Test Case2: Error messages are shown with invalid credentials
Test Case3: Error messages are shown with empty fields
So on...

Images:

!image1.png|thumbnail!
!image2.png|thumbnail!
!image3.png|thumbnail!
!image3.png|thumbnail!
So on...

URLs:

https://abc.com/login
https://abc.com/user/login
So on...

Status: PASS

Progress made:

=> This has been implemented. All things that are mentioned in Ticket's description are done.

=> Please check and let me know if I missed anything OR there's any kind of work that still needs to be done under this card.

CC: Rock, Steve ...

Notes: It is an optional part of a test report. Here you can write some special notes if you want to mention something related to the bug for Project Manager.

Thanks,
Tester Name

This is a basic structure of a test report. Little things can vary as per company requirements, but the basic structure will remain the same.