From 10bfd2be390437d5e8c9af7abb78d9f19b8a15d0 Mon Sep 17 00:00:00 2001
From: FercueNat <113535859+FercueNat@users.noreply.github.com>
Date: Tue, 1 Nov 2022 04:28:52 -0300
Subject: [PATCH] Adding information to Reporting node - QA Roadmap (#2838)
---
.../113-qa/content/106-qa-reporting/readme.md | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/content/roadmaps/113-qa/content/106-qa-reporting/readme.md b/content/roadmaps/113-qa/content/106-qa-reporting/readme.md
index 300292019..d18997101 100644
--- a/content/roadmaps/113-qa/content/106-qa-reporting/readme.md
+++ b/content/roadmaps/113-qa/content/106-qa-reporting/readme.md
@@ -1 +1,11 @@
-# Qa reporting
\ No newline at end of file
+# QA reporting
+
+The International Software Testing Qualifications Board (ISTQB) glossary defines a QA report as: *Documentation summarizing test activities and results*.
+By documenting the testing that was conducted and the results that were achieved, QA reports provide valuable insight into the health of the code base and critical metrics. As such, they should be generated on a regular basis to ensure the quality standards are being met.
+So basically, test reports should document all of the test cases that were performed during software testing, as well as the results of those tests. They should also deliver relevant information about the product and highlight any areas where improvements can be made.
+
+Free Content
+
+How do you write a QA report?
+How To Write QA Test Summary Report? [13 Easy Steps]
+