From 2c949543128711d2a1669e25c0231734bff81ffb Mon Sep 17 00:00:00 2001
From: ChuckD3ath <33813588+ChuckD3ath@users.noreply.github.com>
Date: Sat, 15 Oct 2022 13:29:32 +0200
Subject: [PATCH] Update Functional Testing Types (#2526)

---
 .../100-functional-testing/sanity-testing.md              | 7 ++++++-
 .../100-functional-testing/smoke-testing.md               | 8 +++++++-
 .../107-testing-techniques/100-functional-testing/uat.md  | 7 ++++++-
 3 files changed, 19 insertions(+), 3 deletions(-)

diff --git a/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/sanity-testing.md b/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/sanity-testing.md
index 6a3eb6eee..eaf81902a 100644
--- a/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/sanity-testing.md
+++ b/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/sanity-testing.md
@@ -1 +1,6 @@
-# Sanity testing
\ No newline at end of file
+# Sanity Testing
+
+Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.geeksforgeeks.org/sanity-testing-software-testing/'>Sanity Testing | Software Testing</BadgeLink>
\ No newline at end of file
diff --git a/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/smoke-testing.md b/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/smoke-testing.md
index 141920573..e5f1767a9 100644
--- a/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/smoke-testing.md
+++ b/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/smoke-testing.md
@@ -1 +1,7 @@
-# Smoke testing
\ No newline at end of file
+# Smoke Testing
+
+Smoke Testing is a software testing process that determines whether the deployed software build is stable or not. Smoke testing is a confirmation for QA team to proceed with further software testing. It consists of a minimal set of tests run on each build to test software functionalities.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/smoke-testing.html'>What is Smoke Testing?
+</BadgeLink>
\ No newline at end of file
diff --git a/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/uat.md b/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/uat.md
index 72a0be9ee..f9e31685e 100644
--- a/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/uat.md
+++ b/content/roadmaps/113-qa/content/100-qa-basics/107-testing-techniques/100-functional-testing/uat.md
@@ -1 +1,6 @@
-# Uat
\ No newline at end of file
+# UAT
+
+User Acceptance Testing (UAT) is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment. UAT is done in the final phase of testing after functional, integration and system testing is done.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.guru99.com/user-acceptance-testing.html'>What is User Acceptance Testing (UAT)?</BadgeLink>
\ No newline at end of file