docs: add the glossary terms in the 3 version (#604)

* docs: add the glossary

Signed-off-by: Pratik Mahalle <mahallepratik683@gmail.com>

* fix: update the images and fix some minor issue

Signed-off-by: Pratik Mahalle <mahallepratik683@gmail.com>

* fix: fix some minor changes

Signed-off-by: Pratik Mahalle <mahallepratik683@gmail.com>

---------

Signed-off-by: Pratik Mahalle <mahallepratik683@gmail.com>

Author: pratik-mahalle

static/data/glossaryEntries.js

@@ -44,6 +44,25 @@ export const glossaryEntries = {
       link: "/docs/concepts/reference/glossary/cucumber-testing",
       description: "Uses Gherkin syntax to write readable tests.",
     },
+    {
+      name: "Component Testing",
+      link: "/docs/concepts/reference/glossary/component-testing",
+      description: "Tests individual parts of the application in isolation",
+    },
+  ],
+  D: [
+    {
+      name: "Defect Management",
+      link: "/docs/concepts/reference/glossary/defect-management",
+      description:
+        "Tracks, prioritizes, and resolves bugs to improve software quality.",
+    },
+    {
+      name: "Data Driven Testing",
+      link: "/docs/concepts/reference/glossary/data-driven-testing",
+      description:
+        "Transforming Quality Assurance Through Intelligent Test Automation",
+    },
   ],
   E: [
     {
@@ -70,6 +89,11 @@ export const glossaryEntries = {
       link: "/docs/concepts/reference/glossary/gray-box-testing",
       description: "Tester has partial knowledge of the codebase.",
     },
+    {
+      name: "gRPC",
+      link: "/docs/concepts/reference/glossary/grpc",
+      description: "Revolutionizing Modern API Development",
+    },
   ],
   I: [
     {
@@ -83,6 +107,22 @@ export const glossaryEntries = {
       description: "Same input gives same result every time.",
     },
   ],
+  J: [
+    {
+      name: "JUnit",
+      link: "/docs/concepts/reference/glossary/junit",
+      description:
+        "A popular Java testing framework used to write and run repeatable unit tests.",
+    },
+  ],
+  L: [
+    {
+      name: "Load Testing",
+      link: "/docs/concepts/reference/glossary/load-testing",
+      description:
+        "Tests how the system performs under heavy user or data load.",
+    },
+  ],
   M: [
     {
       name: "Manual Testing",
@@ -100,12 +140,49 @@ export const glossaryEntries = {
       description: "Validates independent services in isolation.",
     },
   ],
+  N: [
+    {
+      name: "Negative Testing",
+      link: "/docs/concepts/reference/glossary/negative-testing",
+      description:
+        "Systematic testing of failures, errors, and unexpected inputs.",
+    },
+  ],
+  O: [
+    {
+      name: "Observability Testing",
+      link: "/docs/concepts/reference/glossary/observability-testing",
+      description: "Building Resilient Systems Through Monitoring Testing",
+    },
+  ],
+  P: [
+    {
+      name: "Performance Testing",
+      link: "/docs/concepts/reference/glossary/performance-testing",
+      description:
+        "Evaluates system speed, stability, and responsiveness under varying conditions.",
+    },
+  ],
+  Q: [
+    {
+      name: "QA Automation",
+      link: "/docs/concepts/reference/glossary/qa-automation",
+      description:
+        "Uses tools and scripts to automate software testing and validation processes.",
+    },
+  ],
   R: [
     {
       name: "Regression Testing",
       link: "/docs/concepts/reference/glossary/regression-testing",
       description: "Ensures new code doesn’t break old features.",
     },
+    {
+      name: "Reliability Testing",
+      link: "/docs/concepts/reference/glossary/reliability-testing",
+      description:
+        "Verifies that the system consistently performs under expected conditions over time.",
+    },
   ],
   S: [
     {
@@ -143,6 +220,13 @@ export const glossaryEntries = {
       description: "Tests specific code components in isolation.",
     },
   ],
+  V: [
+    {
+      name: "Visual Regression Testing",
+      link: "/docs/concepts/reference/glossary/visual-regression-testing",
+      description: "Detects UI bugs by comparing screenshots.",
+    },
+  ],
   W: [
     {
       name: "White Box Testing",

static/img/glossary/What-is-a-Defect.webp

@@ -23,7 +23,7 @@ keywords:
 
 **Gray box testing** is a software testing technique that combines aspects of both black box and white box testing. It involves testing the software with partial knowledge of the internal workings of the application. This means the tester has limited access to the internal structures or algorithms, usually at the level of data structures and algorithms but not at the level of the source code itself.
 
-![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
+![types of testing](../../../../../static/img/glossary/types-of-testing.webp)
 
 ## Why is Gray Box Testing Needed?
 

static/img/glossary/gRPC-architecture.webp

@@ -25,6 +25,7 @@ Black-box testing is a software testing method where the tester evaluates the fu
 The focus lies solely on examining the software's external behavior, inputs, outputs, and responses to different user actions or system interactions.
 
 ![Types of Testing](/img/glossary/types-of-testing.webp)
+
 ## What are the Fundamentals of Black-Box Testing?
 
 This testing approach is essential for several reasons: