Skip to content

Commit 40cebe9

Browse files
authored
Merge branch 'grafana:main' into main
2 parents 427c9bd + 24fae9f commit 40cebe9

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

src/data/markdown/translated-guides/en/06 Test Types/00 Load test types.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,17 +19,17 @@ Start with smoke tests, then progress to higher loads and longer durations.
1919

2020
The main types are as follows. Each type has its own article outlining its essential concepts.
2121

22-
- [**Smoke tests**](../smoke-testing) validate that your script works and that the system performs adequately under minimal load.
22+
- [**Smoke tests**](/test-types/smoke-testing) validate that your script works and that the system performs adequately under minimal load.
2323

24-
- [**Average-load test**](../load-testing) assess how your system performs under expected normal conditions.
24+
- [**Average-load test**](/test-types/load-testing) assess how your system performs under expected normal conditions.
2525

26-
- [**Stress tests**](../stress-testing) assess how a system performs at its limits when load exceeds the expected average.
26+
- [**Stress tests**](/test-types/stress-testing) assess how a system performs at its limits when load exceeds the expected average.
2727

28-
- [**Soak tests**](../soak-testing) assess the reliability and performance of your system over extended periods.
28+
- [**Soak tests**](/test-types/soak-testing) assess the reliability and performance of your system over extended periods.
2929

30-
- [**Spike tests**](../spike-testing) validate the behavior and survival of your system in cases of sudden, short, and massive increases in activity.
30+
- [**Spike tests**](/test-types/spike-testing) validate the behavior and survival of your system in cases of sudden, short, and massive increases in activity.
3131

32-
- [**Breakpoint tests**](../breakpoint-testing) gradually increase load to identify the capacity limits of the system.
32+
- [**Breakpoint tests**](/test-types/breakpoint-testing) gradually increase load to identify the capacity limits of the system.
3333

3434
<Blockquote mod="note" title="">
3535

src/data/markdown/translated-guides/en/06 Test Types/02 Load Testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,5 +103,5 @@ An initial outcome for the average-load test appears during the ramp-up period t
103103

104104
The test validates if the system's performance and resource consumption stay stable during the period of full load, as some systems may display erratic behavior in this period.
105105

106-
Once you know your system performs well and survives a typical load, you may need to push it further to determine how it behaves at above-average conditions. Some of these above-average conditions are known as [Stress tests](../stress-testing).
106+
Once you know your system performs well and survives a typical load, you may need to push it further to determine how it behaves at above-average conditions. Some of these above-average conditions are known as [Stress tests](/test-types/stress-testing).
107107

src/data/markdown/translated-guides/en/06 Test Types/03 Stress testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,4 +104,4 @@ Like the average-load test, an initial outcome for the Stress test shows up duri
104104
During the full load period, verification is vital if the system's performance and resource consumption stays stable with a higher load.
105105

106106
Now that you know that your system can handle outstanding load events, the teams generally check if the system performs well over extended periods.
107-
That is, they run a [Soak test](../soak-testing).
107+
That is, they run a [Soak test](/test-types/soak-testing).

0 commit comments

Comments
 (0)