Skip to content

Commit 7802bb5

Browse files
Fix; boost prominence of graceful stop in concepts
And fix the description
1 parent 8150e10 commit 7802bb5

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/00 Concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ If you know a bit about how scenarios work, you'll design better tests and inter
1212
| On this page | Read about |
1313
|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
1414
| [Open and closed models](/using-k6/scenarios/concepts/open-vs-closed/) | Different ways k6 can schedule VUs, their affects on test results, and how k6 implements the open model in its arrival-rate executors |
15+
| [Graceful Stop](/using-k6/scenarios/concepts/graceful-stop) | A configurable period for iterations to finish or ramp down after the test reaches its scheduled duration |
1516
| [Arrival-rate VU allocation](/using-k6/scenarios/concepts/arrival-rate-vu-allocation/) | How k6 allocates VUs in arrival-rate executors |
1617
| [Dropped iterations](/using-k6/scenarios/concepts/dropped-iterations/) | Possible reasons k6 might drop a scheduled iteration |
17-
| [Graceful Stop](/using-k6/scenarios/concepts/graceful-stop) | A configurable period to let iterations finish or ramp down after the test has reached it's scheduled duration |
1818

File renamed without changes.

0 commit comments

Comments
 (0)