HTTP Archive files - Defect Logging
In the conventional testing, QA when reporting the defects utilize the classical method of giving data and some of the formats look like below
- Giving a great title to explain the defects
- Steps to replicate
- Expected result
- Actual result
- Screenshots
- Loom videos etc..
Even after having all these data in the Defect Management tools like JIRA, when a developer tries to debug it might be time-consuming to identify the area and apply a fix. Particularly when a hot patch has to be applied in prod server then the time consumed in understanding and applying the proper fix plays a very crucial role.
HAR files
HAR files are simply the network calls which are made browser's console. Technically speaking HAR file is the HTTP Archive file in JSON format which gives detailed information of the network calls made on a browser.
This information includes,
- Request made on browser
- Response data
- Parameters sent while perming a request call
How does HAR file help a developer...?
HAR files get created by recording the network calls of the browser. Having the record of the network calls made on a machine would help the developer in better understanding of the scenario.
How to create a HAR file..?
- While starting a scenario the user (QA) can open the browser network console and enable "Preserve log" check-box.
- Clear the existing network calls from the network console and star the scenario of defect.
- After the scenario is completed, right click on any network call and click on "Save as HAR with content" and save the file in format <filename>.har.
- QA can then upload this file while logging the defect.
Conclusion: Even though files like screenshots or loom videos explain the way to reproduce the defect and also sometime pave the way to fix the defect. Companies which included HAR files in their defect logging systems, have proved to have a great impact in defect resolution.