docs: link regression testing glossary references to the blog guide

versioned_docs/version-4.0.0/concepts/reference/glossary/behaviour-driven-development.md

@@ -234,7 +234,7 @@ The approaches work together. Many teams use BDD scenarios to define features at
 - **Needs real business involvement:** if only developers write scenarios, BDD becomes extra syntax on top of ordinary tests.
 - **Maintenance overhead:** large suites with duplicated or overly detailed steps become slow and fragile.
 - **Learning curve:** writing good scenarios is a skill, and early suites are often too imperative.
-- **Not full coverage:** BDD scenarios cover key behaviors, not every code path. You still need [unit](/docs/concepts/reference/glossary/unit-testing/), [integration](/docs/concepts/reference/glossary/integration-testing/) and [regression](/docs/concepts/reference/glossary/regression-testing/) tests.
+- **Not full coverage:** BDD scenarios cover key behaviors, not every code path. You still need [unit](/docs/concepts/reference/glossary/unit-testing/), [integration](/docs/concepts/reference/glossary/integration-testing/) and [regression](https://keploy.io/blog/community/regression-testing-an-introductory-guide) tests.
 
 ### When BDD may not be a good fit
 

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

@@ -148,7 +148,7 @@ Black-box testing is a valuable tool for ensuring the quality of software. It ca
 - [White Box Testing](/docs/concepts/reference/glossary/white-box-testing/) — the opposite, code-aware testing approach.
 - [Grey Box Testing](/docs/concepts/reference/glossary/gray-box-testing/) — combines black-box and white-box techniques.
 - [Functional Testing](/docs/concepts/reference/glossary/functional-testing/) — verifies behavior without internal knowledge.
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — often done via black-box test cases.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — often done via black-box test cases.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.
 
 ## FAQ

versioned_docs/version-4.0.0/concepts/reference/glossary/data-driven-testing.md

@@ -85,7 +85,7 @@ Focus on high-value scenarios where multiple data combinations are essential. Lo
 
 - [Test Data Generation](/docs/concepts/reference/glossary/test-data-generation/) — supplies the data sets these tests consume.
 - [QA Automation](/docs/concepts/reference/glossary/qa-automation/) — data-driven tests are typically automated.
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — reruns many data sets to catch regressions.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — reruns many data sets to catch regressions.
 - [Cucumber Testing](/docs/concepts/reference/glossary/cucumber-testing/) — supports data-driven scenarios via examples tables.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.
 

versioned_docs/version-4.0.0/concepts/reference/glossary/defect-management.md

@@ -257,7 +257,7 @@ Let's continue to pursue excellence in software quality!
 ## Related Terms
 
 - [Software Testing Life Cycle](/docs/concepts/reference/glossary/software-testing-life-cycle/) — defect management spans the whole cycle.
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — verifies fixed defects stay fixed.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — verifies fixed defects stay fixed.
 - [Error Guessing](/docs/concepts/reference/glossary/error-guessing/) — a technique for uncovering defects.
 - [Acceptance Testing](/docs/concepts/reference/glossary/acceptance-testing/) — catches defects before release.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.

versioned_docs/version-4.0.0/concepts/reference/glossary/end-to-end-testing.md

@@ -70,7 +70,7 @@ End-to-end (E2E) testing is a important component of the software development pr
 - [Integration Testing](/docs/concepts/reference/glossary/integration-testing/) — checks module interactions before E2E.
 - [Acceptance Testing](/docs/concepts/reference/glossary/acceptance-testing/) — validates the finished product for users.
 - [Mocks](/docs/concepts/reference/glossary/mocks/) — Keploy uses mocks to replay E2E dependencies.
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — reruns E2E flows to catch regressions.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — reruns E2E flows to catch regressions.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.
 
 ## FAQs

versioned_docs/version-4.0.0/concepts/reference/glossary/functional-testing.md

@@ -229,7 +229,7 @@ Despite the challenges, functional testing is an important part of the software
 
 - [Black Box Testing](/docs/concepts/reference/glossary/black-box-testing/): functional testing is largely black-box.
 - [Integration Testing](/docs/concepts/reference/glossary/integration-testing/): a functional testing type for module interactions.
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/): re-verifies functionality after changes.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide): re-verifies functionality after changes.
 - [Unit Testing](/docs/concepts/reference/glossary/unit-testing/): the most granular functional test level.
 - [Browse all testing terms](/docs/concepts/reference/glossary/): the full Keploy glossary.
 

versioned_docs/version-4.0.0/concepts/reference/glossary/manual-testing.md

@@ -61,6 +61,6 @@ Overall, by automating testing processes with Keploy, you can improve testing ef
 ## Related Terms
 
 - [QA Automation](/docs/concepts/reference/glossary/qa-automation/) — automate repetitive manual test execution.
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — re-run manual test cases after code changes.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — re-run manual test cases after code changes.
 - [Unit Testing](/docs/concepts/reference/glossary/unit-testing/) — a foundational automated alternative to manual checks.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.

versioned_docs/version-4.0.0/concepts/reference/glossary/qa-automation.md

@@ -152,7 +152,7 @@ QA automation is essential for modern software development. It enables **faster
 
 ## Related Terms
 
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — a prime candidate for automation.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — a prime candidate for automation.
 - [Unit Test Automation](/docs/concepts/reference/glossary/unit-test-automation/) — automate tests at the unit level.
 - [Manual Testing](/docs/concepts/reference/glossary/manual-testing/) — the approach QA automation replaces or complements.
 - [Performance Testing](/docs/concepts/reference/glossary/performance-testing/) — automate load and speed checks.

versioned_docs/version-4.0.0/concepts/reference/glossary/software-testing-life-cycle.md

@@ -85,7 +85,7 @@ Incorporating STLC best practices and leveraging advanced testing tools empower
 
 ## Related Terms
 
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — a key phase within the STLC.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — a key phase within the STLC.
 - [Defect Management](/docs/concepts/reference/glossary/defect-management/) — track defects reported during testing.
 - [QA Automation](/docs/concepts/reference/glossary/qa-automation/) — automate STLC test execution phases.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.

versioned_docs/version-4.0.0/concepts/reference/glossary/unit-test-automation.md

@@ -53,7 +53,7 @@ Unit test automation offers many advantages, including:
   **Example**: For a new developer onboarding to a project, unit tests for functions like `processPayment()` demonstrate expected behavior, helping them understand how to use and integrate the function.
 
 - **Regression Testing**:  
-  Unit tests act as a form of [regression testing](https://keploy.io/docs/concepts/reference/glossary/regression-testing), quickly alerting developers to unintended changes after updates or modifications.  
+  Unit tests act as a form of [regression testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide), quickly alerting developers to unintended changes after updates or modifications.\
   **Example**: If a developer modifies the `applyCoupon()` function, running the associated unit tests will immediately indicate if the changes inadvertently affected other functionalities, maintaining consistency across updates.
 
 In addition to the benefits listed above, unit test automation can also help to:

versioned_docs/version-4.0.0/concepts/reference/glossary/visual-regression-testing.md

@@ -153,7 +153,7 @@ Visual regression testing continues to evolve as applications become more comple
 
 ## Related Terms
 
-- [Regression Testing](/docs/concepts/reference/glossary/regression-testing/) — visual regression is a specialized form of it.
+- [Regression Testing](https://keploy.io/blog/community/regression-testing-an-introductory-guide) — visual regression is a specialized form of it.
 - [Functional Testing](/docs/concepts/reference/glossary/functional-testing/) — complements visual checks with behavior validation.
 - [Component Testing](/docs/concepts/reference/glossary/component-testing/) — test isolated UI components visually.
 - [Browse all testing terms](/docs/concepts/reference/glossary/) — the full Keploy glossary.