Follow along to learn how to:
- Run a test.
- Add virtual users.
- Increase the test duration.
- Ramp the number of requests up and down as the test runs.
With these example snippets, you'll run the test with your machine's resources. But, if you have a k6 Cloud account, you can also use the k6 cloud command to outsource the test to k6 servers.
To run a simple local script:
Copy the following code, paste it into your favorite editor, and save it as script.js:script.js
Then, run k6 with this command:CLIDockerDocker in Win PowerShell
Now run a load test with more than one virtual user and a longer duration:
Running a 30-second, 10-VU load test
For a test to run, you need to have init code, which prepares the test, and VU code, which makes requests.
Code in the init context defines functions and configures the test options (like duration).
Every test also has a default function. This function defines the entry point for your VUs.
Init code runs first and is called only once per VU. On the other hand, default code executes as many times as the test options set.
Then, run the script without those options on the command line:
You can ramp the number of VUs up and down during the test. To configure ramping, use the options.stages property.
For advanced ramping, you can use scenarios and the ramping-vus executor.
Portability is a major design goal of k6
You can run the same test in different modes with minimal changes.
k6 supports three execution modes to run a k6 test: local, distributed, and cloud.
Local: the test execution happens entirely on a single machine, container, or CI server.
Distributed: the test execution is distributed across a Kubernetes cluster.Runningk6-resource.yaml
Cloud: the test execution happens on k6 Cloud.