From 98fdb6aa912dba7dcc3ae9fa320e62be18a24b69 Mon Sep 17 00:00:00 2001
From: Ardi Setiawan <111270813+ardizanki@users.noreply.github.com>
Date: Mon, 5 Sep 2022 16:17:52 +0700
Subject: [PATCH] Add QA reporting content (#1697)

report free content - az
---
 .../113-qa/content/102-qa-manual-testing/103-reporting.md    | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/content/roadmaps/113-qa/content/102-qa-manual-testing/103-reporting.md b/content/roadmaps/113-qa/content/102-qa-manual-testing/103-reporting.md
index 704f65445..fc08cda37 100644
--- a/content/roadmaps/113-qa/content/102-qa-manual-testing/103-reporting.md
+++ b/content/roadmaps/113-qa/content/102-qa-manual-testing/103-reporting.md
@@ -1,3 +1,8 @@
 # Reporting
 
 Communicating the QA and testing team outputs can be interpreted in several different ways. Having a solid reporting stream is very essential for all the decisions that a stakeholder/manager can take.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/defect-management-process.html'>Defect Management Process in Software Testing</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://automationhacks.io/2020/07/25/writing-clear-bug-reports/'>Writing clear bug reports</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.ministryoftesting.com/dojo/series/the-testing-planet-2019/lessons/the-art-of-the-bug-report'>The Art Of The Bug Report</BadgeLink>