Revert "fix: the-broken-link-of-glossary"

versioned_docs/version-2.0.0/concepts/reference/glossary/black-box-testing.md

@@ -25,7 +25,7 @@
 
 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](/static/img/glossary/types-of-testing.webp)
+![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
 
 ## What are the Fundamentals of Black-Box Testing?
 
@@ -52,7 +52,7 @@
 5. **Detection of Defects**: Identifies functional errors, security vulnerabilities, and performance bottlenecks.
 6. **Accessibility**: Suitable for testers with diverse backgrounds and skill sets, adaptable to various software applications.
 
 ## Whate are types of Black-Box Testing Techniques ?
 
 ![How Black Box testing Works?](https://keploy-devrel.s3.us-west-2.amazonaws.com/thumbnail_Black-box.jpg)
 
@@ -63,7 +63,7 @@
 **Example:** Consider a login screen for a web application that requires users to enter their username and password. In equivalence partitioning, we can identify three equivalence classes for each input:
 
 - _Valid username_: Any valid username (e.g., "user123")
 - _Invalid username_: Username that doesn't exist in the system (e.g., "invaliduser")
 - _Empty username_: No username provided
 
 Similarly, for the password field, we can identify equivalence classes such as:

versioned_docs/version-2.0.0/concepts/reference/glossary/code-coverage.md

@@ -41,7 +41,7 @@ It's analysis provides several benefits:
 
 Keploy has native integrations with your unit-testing libraries like go-test, jUnit, jest, pyTest. Keploy gives combined test-coverage and can also be integrated in existing CI pipelines easily within go-test, jUnit, jest, pyTest workflows.
 
-![Keploy Test Replay](https://keploy.io/docs/gif/replay-tc.gif)
+<img scr="https://keploy.io/docs/gif/replay-tc.gif?raw=true"/>
 
 By generating additional tests that exercise different parts of your codebase, you can increase the percentage of code that is covered by your tests. For example, in case of NodeJS application you can use Jest. Jest provides a built-in code coverage tool that can help you measure the effectiveness of your tests and identify areas of the code that need additional testing. By adding Keploy SDK with Jest, you can easily generate test cases and increase your code coverage. Let's create a `Keploy.test.js`
 

versioned_docs/version-2.0.0/concepts/reference/glossary/white-box-testing.md

@@ -28,7 +28,7 @@
 
 The primary goal of white box testing is to validate the software's internal operations, ensuring that it functions correctly and efficiently. This involves checking all pathways and conditions, optimizing code for speed and performance, and ensuring that there are no hidden errors.
 
-![Types of Testing](/static/img/glossary/types-of-testing.webp)
+![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
 
 ## Fundamentals of White Box Testing
 
@@ -99,7 +99,7 @@
 | Skill Level            | Requires specialized technical skills           | Can be performed by testers with various skill levels |
 | Types of Defects Found | Internal logic errors, security vulnerabilities | Functional, usability, and performance issues         |
 
 ## How to perform Whitebox testing with Keploy ?
 
 Firstly, install [Keploy](https://keploy.io/), a testing tool that helps you automate the testing process. Here’s how you can perform white box testing with Keploy:
 
@@ -113,7 +113,7 @@
 
 - **Error Analysis and Debugging:** Utilize Keploy’s built-in error analysis tools to identify and resolve issues within your code. Keploy provides detailed insights into errors, helping you quickly pinpoint and fix problems in the internal logic of your application.
 
 - C**ontinuous Integration and Testing:** Integrate Keploy with your CI pipeline to automate white box testing. This ensures that internal testing is part of your regular development workflow, helping maintain high code quality and quickly catch regressions or new issues.
 
 ## Conclusion
 

versioned_docs/version-3.0.0/concepts/reference/glossary/white-box-testing.md

@@ -28,7 +28,7 @@ White box testing, also known as clear box or glass box testing, is a software t
 
 The primary goal of white box testing is to validate the software's internal operations, ensuring that it functions correctly and efficiently. This involves checking all pathways and conditions, optimizing code for speed and performance, and ensuring that there are no hidden errors.
 
-![Types of Testing](/static/img/glossary/types-of-testing.webp)
+![types of testing](../../../../../static/img/glossary/types-of-testing.jpeg)
 
 ## Fundamentals of White Box Testing