Add and fix links to test types

Author: ppcano

src/components/pages/doc-welcome/use-cases/use-cases.view.js

@@ -27,8 +27,8 @@ export const UseCases = () => {
               className={'link'}
               to={
                 urlLocale === 'es'
-                  ? '/es/tipos-de-prueba/stress-testing/#spike-testing'
-                  : '/test-types/stress-testing#spike-testing-in-k6'
+                  ? '/test-types/spike-testing/'
+                  : '/test-types/spike-testing/'
               }
             >
               spike

src/data/markdown/docs/20 jslib/01 jslib/10 expect.md

@@ -18,7 +18,7 @@ The `expect` module is a JavaScript library that simplifies specifying expectati
 
 This library is especially useful for:
  - Functional testing, where many asserts are needed
- - Stress testing, where the System Under Test is failing and the test code needs to stay robust.
+ - [Stress testing](/test-types/stress-testing/), where the System Under Test is failing and the test code needs to stay robust.
  - Load testing, where the failures of the System Under Test need to be robustly collected for analysis
 
 > ⭐️ Source code available on [GitHub](https://github.com/k6io/k6-jslib-expect). 

src/data/markdown/translated-guides/en/08 Testing Guides/01 API load testing.md

@@ -67,12 +67,12 @@ Even if the test logic stays the same, its load might change.
 The test goal determines the test type, which in turn determines the test load.
 Consider the following test types, which correspond to different goals load profiles:
 
-- [Smoke test](https://k6.io/docs/test-types/smoke-testing). Verify the system functions with minimal load.
-- [“Average” load test](https://k6.io/docs/test-types/load-testing/). Discover how the system functions with typical traffic.
-- [Stress test](https://k6.io/docs/test-types/stress-testing). Discover how the system functions with the load of peak traffic.
-- [Spike test](https://k6.io/docs/test-types/stress-testing#spike-testing-in-k6). Discover how the system functions with sudden and massive increases in traffic.
-- [Breaking test](https://github.com/grafana/k6-learn/blob/main/Modules/I-Performance-testing-principles/03-Load-Testing.md#breakpoint-test). Progressively ramp traffic to discover system breaking points.
-- [Soak test](https://k6.io/docs/test-types/soak-testing). Discover whether or when the system degrades under loads of longer duration.
+- [Smoke test](/docs/test-types/smoke-testing). Verify the system functions with minimal load.
+- [“Average” load test](/test-types/load-testing/). Discover how the system functions with typical traffic.
+- [Stress test](/test-types/stress-testing). Discover how the system functions with the load of peak traffic.
+- [Spike test](/test-types/spike-testing). Discover how the system functions with sudden and massive increases in traffic.
+- [Breakpoint test](/test-types/breakpoint-testing/). Progressively ramp traffic to discover system breaking points.
+- [Soak test](/test-types/soak-testing). Discover whether or when the system degrades under loads of longer duration.
 
 The test types that you choose inform how you plan and structure your test.
 But each application, organization, and testing project differs.

src/data/markdown/translated-guides/en/08 Testing Guides/04 Running large tests.md

@@ -102,7 +102,7 @@ If you're close to exhausting available physical RAM, the system might start swa
 
 ## Error handling should be resilient
 
-When running large stress tests, your script shouldn't assume anything about the HTTP response.
+When running [large stress tests](/test-types/stress-testing/), your script shouldn't assume anything about the HTTP response.
 An oversight of some scripts is to test with only the [happy path](/misc/glossary#happy-path "The default behavior that happens when the system returns no errors") in mind.
 
 For example, in k6 scripts, we often see something like this _happy path_ check:

src/data/markdown/translated-guides/es/05 Test Types/00 Introduction.md

@@ -13,7 +13,7 @@ Cada tipo de prueba está diseñado para proporcionarle diferentes conocimientos
 
 [Load Test (Prueba de Carga)](/es/tipos-de-prueba/load-testing/): se ocupa principalmente de evaluar el rendimiento de su sistema en términos de usuarios concurrentes o solicitudes por segundo.
 
-[Stress Test (Prueba de Estrés)](/es/tipos-de-prueba/stress-testing/) y [Spike testing (Prueba de Pico)](/es/tipos-de-prueba/stress-testing/#spike-testing-en-k6): se ocupan de evaluar los límites de su sistema y la estabilidad en condiciones extremas.
+[Stress Test (Prueba de Estrés)](/es/tipos-de-prueba/stress-testing/) y [Spike testing (Prueba de Pico)](/test-types/spike-testing/): se ocupan de evaluar los límites de su sistema y la estabilidad en condiciones extremas.
 
 [Soak Test (Prueba de Resistencia)](/es/tipos-de-prueba/soak-testing/): le informa sobre la fiabilidad y el rendimiento de su sistema durante un periodo de tiempo prolongado.
 

src/data/markdown/versioned-js-api/v0.32/javascript api/02 k6/sleep- t -.md

@@ -8,7 +8,7 @@ Suspend VU execution for the specified duration.
 
 `sleep` is the primary means of introducing delays in your script. These delays aim to represent the time it would take a real user to parse a page before proceeding to the next page, commonly referred to as "think time". Without `sleep` statements, a script will run as quickly as the system it runs on allows it, as well as by how fast the server(s) it communicates with responds (because k6 executes HTTP requests synchronously).
 
-Unless you are stress testing and want each VU to execute as many requests per second as possible, you should include `sleep` statements throughout the script.
+Unless you are [stress testing](/test-types/stress-testing/) and want each VU to execute as many requests per second as possible, you should include [`sleep`](/javascript-api/k6/sleep/) statements throughout the script.
 This relates your VU behavior more closely to the behavior of real users.
 
 Ideally, you would also feed in a randomized pause duration, further encouraging natural concurrency to develop.