diff options
Diffstat (limited to 'doc/ci/testing/load_performance_testing.md')
| -rw-r--r-- | doc/ci/testing/load_performance_testing.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/testing/load_performance_testing.md b/doc/ci/testing/load_performance_testing.md index 549aa10287e..6b16f15a9d9 100644 --- a/doc/ci/testing/load_performance_testing.md +++ b/doc/ci/testing/load_performance_testing.md @@ -59,7 +59,7 @@ Configuring your Load Performance Testing job can be broken down into several di ### Determine the test parameters -The first thing you need to do is determine the [type of load test](https://k6.io/docs/test-types/introduction) +The first thing you need to do is determine the [type of load test](https://k6.io/docs/test-types/load-test-types/) you want to run, and how you want it to run (for example, the number of users, throughput, and so on). Refer to the [k6 docs](https://k6.io/docs/), especially the [k6 testing guides](https://k6.io/docs/testing-guides), @@ -79,7 +79,7 @@ We strongly recommend [not running these tests against a production environment] ### Write the load performance test After the environment is prepared, you can write the k6 test itself. k6 is a flexible -tool and can be used to run [many kinds of performance tests](https://k6.io/docs/test-types/introduction). +tool and can be used to run [many kinds of performance tests](https://k6.io/docs/test-types/load-test-types/). Refer to the [k6 documentation](https://k6.io/docs/) for detailed information on how to write tests. ### Configure the test in GitLab CI/CD @@ -151,7 +151,7 @@ The CI/CD YAML configuration example above works for testing against static envi but it can be extended to work with [review apps](../review_apps/index.md) or [dynamic environments](../environments/index.md) with a few extra steps. -The best approach is to capture the dynamic URL in a [`.env` file](https://docs.docker.com/compose/env-file/) +The best approach is to capture the dynamic URL in a [`.env` file](https://docs.docker.com/compose/environment-variables/env-file/) as a job artifact to be shared, then use a custom CI/CD variable we've provided named `K6_DOCKER_OPTIONS` to configure the k6 Docker container to use the file. With this, k6 can then use any environment variables from the `.env` file in scripts using standard JavaScript, |