stress-testing.md

title	description
Stress Testing	Stress Testing is a type of testing that inspects the stability and reliability of your application under realistic or extreme conditions — depending on the scenario you setup. For example, you can use stress testing to verify that your application can handle a large number of requests or that it can handle a large amount of data.

Stress Testing

Stress Testing is a type of testing that inspects the stability and reliability of your application under realistic or extreme conditions — depending on the scenario you setup. For example, you can use stress testing to verify that your application can handle a large number of requests or that it can handle a large amount of data.

<iframe width="560" height="315" src="https://www.youtube.com/embed/SaMoPZwdOCY?si=KBskkVWLUUSyK0u0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

In Pest, you can combine the power of Stress Testing with the Expectation API ensuring no stability and reliability regressions over time. This can be useful to verify that your application is stable and reliable after a new release, or after a new deployment.

Behind the scenes, this project utilizes k6, a powerful open-source load testing tool for evaluating the performance of APIs, microservices, and websites. k6 is licensed under the AGPL-3.0 License, and the k6 binary is downloaded when the plugin is used for the first time.

To start using Pest's Stress Testing plugin (mostly known as Stressless), you need to require the stressless plugin via Composer.

composer require pestphp/pest-plugin-stressless --dev

After requiring the plugin, you may start using it in two different ways:

• Using the stress command: It's useful when you want to quickly stress test a URL, without setting expectations on the result.
• Using the stress() function: It's useful when you want to stress test a URL and set expectations on the result.

Testing external domain or local IP Address? When load testing a domain from an external network, you get a realistic picture of how your application performs under typical user loads. This includes factors like network latency and real-world internet traffic. However, when testing a local IP address within your network, the focus is on understanding the performance of your internal infrastructure in a controlled environment, without external variables like internet or DNS resolution times. It's particularly useful for identifying potential bottlenecks within your own network or server and for performance tuning of internal applications or servers. This includes tasks such as configuring PHP FPM more effectively, etc.

The Stress Command

The stress command is useful when you want to quickly stress test a URL, analyze the result, and all without setting expectations on the result. It's the quickest way to launch a stress test, and it happens directly on the terminal.

To get started, you may use the stress command and provide the URL you wish to stress test:

./vendor/bin/pest stress example.com

By default, the stress test duration will be 5 seconds. However, you may customize this value using the --duration option:

./vendor/bin/pest stress example.com --duration=5

In addition, the number of concurrent requests will be 1. However, you may also customize this value using the --concurrency option:

./vendor/bin/pest stress example.com --concurrency=5

The concurrency value represents the number of concurrent requests that will be made to the given URL. For example, if you set the concurrency to 5, Pest will constantly make 5 concurrent requests to the given URL until the stress test duration is reached.

You may want to be mindful of the number of concurrent requests you configure. If you configure too many concurrent requests, you may overwhelm your application, server or hit rate limits / firewalls.

If you want to specify the http method used for the stress test, you can use one of the provided delete, get, head, options, patch, put or post options. Using options, patch and put options, you can specify an optional payload argument to be used in the requests. Using post option, you are required to provide the payload argument.

./vendor/bin/pest stress example.com/articles
# or
./vendor/bin/pest stress example.com/articles --get
# or
./vendor/bin/pest stress example.com/articles --head
# or
./vendor/bin/pest stress example.com/articles --options
# or
./vendor/bin/pest stress example.com/articles --options='{"name": "Nuno"}'
# or
./vendor/bin/pest stress example.com/articles/1 --patch
# or
./vendor/bin/pest stress example.com/articles/1 --patch='{"name": "Nuno"}'
# or
./vendor/bin/pest stress example.com/articles --put
# or
./vendor/bin/pest stress example.com/articles --put='{"name": "Nuno"}'
# or
./vendor/bin/pest stress example.com/articles --post='{"name": "Nuno"}'
# or
./vendor/bin/pest stress example.com/articles/1 --delete

Once the stress test is completed, Pest will display a summary of the stress test result.

The Stress function

Once you start understanding how stress testing works, you may want to start setting expectations on the stress test result. For example, you may want to verify that the average response time is always less than 100ms, and this is where the stress() function comes in.

To get started, simply create a regular test and use the stress() function to stress test a given URL:

<?php

use function Pest\Stressless\stress;

it('has a fast response time', function () {
    $result = stress('example.com');

    expect($result->requests()->duration()->med())->toBeLessThan(100); // < 100.00ms
});

By default, the stress test duration will be 10 seconds. However, you may customize this value using the for()->seconds() method:

$result = stress('example.com')->for(5)->seconds();

In addition, the number of concurrent requests will be 1. However, you may also customize this value using the concurrently method:

$result = stress('example.com')->concurrently(requests: 2)->for(5)->seconds();

At any time, you may dd the stress test result to see its details like if you were using the stress command):

$result = stress('example.com')->dd();
                             //->dump();
                             //->verbosely();

If you want to specify the http method used for the stress test, you can use one of the provided delete, get, head, options, patch, put or post methods. Using options, patch and put methods, you can specify an optional payload argument to be used in the requests. Using post method, you are required to provide the payload argument.

$result = stress('example.com/articles/1')->delete();
// or
$result = stress('example.com/articles')->get();
// or
$result = stress('example.com/articles')->head();
// or
$result = stress('example.com/articles')->options();
// or
$result = stress('example.com/articles')->options(["name" => "Nuno"]);
// or
$result = stress('example.com/articles/1')->patch();
// or
$result = stress('example.com/articles/1')->patch(["name" => "Nuno"]);
// or
$result = stress('example.com/articles')->put();
// or
$result = stress('example.com/articles')->put(["name" => "Nuno"]);
// or
$result = stress('example.com/articles')->post(["name" => "Nuno"]);

The stress() function return the stress test result, which you can use to set expectations. Here is the list of available methods:

Request Duration

Returns the overall request duration in milliseconds.

$result->requests()->duration()->med();
                            // ->min();
                            // ->max();
                            // ->p90();
                            // ->p95();

Requests Count

Returns the number of requests made.

$result->requests()->count();

Requests Rate

Returns the number of requests made per second.

$result->requests()->rate();

Requests Failed Count

Returns the number of requests that failed.

$result->requests()->failed()->count();

Requests Failed Rate

Returns the number of requests that failed per second.

$result->requests()->failed()->rate();

Requests Time To First Byte Duration / TTFB

Returns the request time to first byte duration in milliseconds.

$result->requests()->ttfb()->duration()->med();
                                    // ->min();
                                    // ->max();
                                    // ->p90();
                                    // ->p95();

Requests DNS Lookup Duration

This metric is affected by the network latency between the client and the DNS server.

Returns the request DNS lookup duration in milliseconds.

$result->requests()->dnsLookup()->duration()->med();
                                         // ->min();
                                         // ->max();
                                         // ->p90();
                                         // ->p95();

Requests TLS Handshaking Duration

This metric is affected by the network latency between the client and the server.

Returns the request TLS handshaking duration in milliseconds.

$result->requests()->tlsHandshaking()->duration()->med();
                                              // ->min();
                                              // ->max();
                                              // ->p90();
                                              // ->p95();

Requests Download Duration

This metric is affected by the network latency between the client and the server.

Returns the request download duration in milliseconds.

$result->requests()->download()->duration()->med();
                                        // ->min();
                                        // ->max();
                                        // ->p90();
                                        // ->p95();

Requests Download Data Count

Returns the request download data count in bytes.

$result->requests()->download()->data()->count();

Requests Download Data Rate

Returns the request download data rate in bytes per second.

$result->requests()->download()->data()->rate();

Requests Upload Duration

This metric is affected by the network latency between the client and the server.

Returns the request upload duration in milliseconds.

$result->requests()->upload()->duration()->med();
                                      // ->min();
                                      // ->max();
                                      // ->p90();
                                      // ->p95();

Requests Upload Data Count

Returns the request upload data count in bytes.

$result->requests()->upload()->data()->count();

Requests Upload Data Rate

Returns the request upload data rate in bytes per second.

$result->requests()->upload()->data()->rate();

Test Run Concurrency

Returns the number of concurrent requests made during the stress test, which is the value you set using the --concurrency option or the concurrently method.

$result->testRun()->concurrency();

Test Run Duration

Returns the duration of the stress test, which is the value you set using the --duration option or the for()->seconds() method.

$result->testRun()->duration();

---

Here, we've seen how to use Pest's Stress Testing plugin (aka stressless) to stress test a given URL and set expectations on the result. Moving on, let's explore how to test the coverage of your testing code: Test Coverage