Artillery v2.0.34

New features

Core & CLI

• Add artillery ping command for quick testing of HTTP endpoints. Sends a request to a URL and shows a performance breakdown (DNS/TCP/TLS/TTFB/download timings) and response headers. Supports expectations via --expect, JMESPath and Cheerio queries on the response body, custom headers, basic auth, JSON/form request bodies, and HTTP/2 (default) or HTTP/1.1
• Full support for ESM: in processors, plugins, engines and custom reporters, including modules that use top-level await
• TypeScript type definitions shipped with the artillery package now model the full test script: all arrival phase kinds, scenarios for every built-in engine, capture/match, built-in plugin configs, and processor hook contracts.

AWS Lambda & Fargate

• Add --aws-tags flag to apply custom tags to AWS resources created for a test run (Fargate tasks, Lambda functions, SQS queues). Example: --aws-tags "team:perf,cost-center:1234"

Playwright

• Upgrade to Playwright v1.62.1

Fixes & improvements

Core & CLI

• Fix issue where tests using relative imports (e.g. import x from './helpers.js') in processor code could fail to run
• Fix issue where metric renaming via $rewriteMetricName was silently ignored when the processor file was an ES module

AWS Lambda & Fargate

• The fake-data plugin is now bundled with the worker image. Previously workers downloaded it from the npm registry at test startup

Docker

• Scripts mounted into the official Docker image can now import dependencies bundled with Artillery, such as Playwright

Other changes

• Various dependency upgrades to address security advisories
• npm releases are now published via npm trusted publishing (OIDC) with provenance attestations

Artillery v2.0.33

What's changed

• Upgrade to Playwright v1.61.0 (#3746)
• Replace Falso with Faker.js in fake-data plugin (#3745)

Artillery v2.0.32

Artillery v2.0.32

What's Changed

New features

Playwright

• Upgrade to Playwright v1.60.0 #3737

Fixes & improvements

Core

• Fix issue where http.timeout was silently capped at 8 seconds for slow origins. Requests against backends that took more than 8 seconds to send the first response byte would fail with ERR_SOCKET_TIMEOUT regardless of the configured http.timeout value. #3730
• Fix issue where Artillery commands could fail at startup with MODULE_NOT_FOUND errors for @smithy/node-config-provider and @smithy/config-resolver. #3736 #3735

AWS ECS/Fargate

• Fix issue where tests that depend on external npm modules could run with fewer VUs than configured due to undetected worker startup errors. #3739

Artillery Cloud

• Fix regression where errors from trace upload requests were not surfaced in the CLI output. #3734
• Improve reliability of sending metrics and events to Artillery Cloud. #3731

Other improvements & fixes

• Improved dependency detection for tests that use external npm modules. #3728

Dependencies

• Update OpenTelemetry exporter dependencies #3740
• Various dependency upgrades

---

with contributions from @maikefischer

Artillery v2.0.31

New features

HTTP engine

• Add support for W3C Trace Context propagation on outgoing HTTP requests. Enable via config.http.distributedTracing (boolean, or object with enabled, sampled, and traceIdPrefix fields). When enabled, Artillery adds a traceparent header to each request so backend traces can be correlated with the originating test. #3708

AWS Fargate

• Add CLI heartbeat mechanism for scenarios where the CLI exits abnormally (e.g. with SIGKILL) and worker tasks continue running . Fargate worker tasks will now self-terminate if the CLI disappears for more than 180 seconds. #3705

Slack plugin

• Add notifyOnFailureOnly option to only send a Slack notification when a test fails. #3714

Playwright

• Upgrade to Playwright v1.59.1 #3719

Fixes & improvements

AWS Lambda

• Fix issue where test data with npm dependencies (for example, TypeScript scenarios that require external packages) could silently skip installation, causing the test to fail later with module-not-found errors. 1825591

Core

• Upgrade the HTTP engine to Got v14.6.6 (from Got v11). #3702 Potentially breaking change if your tests use hooks that access or modify Got internals.

Azure ACI

• Test artifacts in Blob Storage are now retained by default. To automatically remove old artifacts, configure a lifecycle management policy on the storage account. #3722

OpenTelemetry

• Upgrade the OpenTelemetry JS SDK to 2.x. Artillery now emits both the legacy and current semantic attribute names on spans (for example http.url alongside url.full, and http.method alongside http.request.method) so existing dashboards and queries continue to work. #3700

Other improvements & fixes

• Worker images used on AWS Fargate, Lambda and Azure ACI are now based on the official Docker Hardened Node.js image #3717
• Routine dependency upgrades to address CVEs #3723 #3701 #3721 #3704

Artillery v2.0.30

• Upgrade to Playwright v1.58.1 (#3692)
• Fix: ensure that when running tests on Fargate, the pre-packaged versions of Playwright / Artillery CLI are always used, and not reinstalled as dependencies. This fixes Playwright browser binary mismatch errors under some conditions. (#3693)

Artillery v2.0.29

• Upgrade to Playwright v1.58.0 (#3687)
• AWS Fargate: fix issue where tests that track many distinct metrics could report incomplete results (#3684)

Artillery v2.0.28

New features

• Add query string normalization to reduce the number of distinct metrics in Playwright tests. Two new configuration options are now available:
  • stripQueryString (defaults to false): Remove query strings from URLs
  • normalizeQueryString (defaults to true): Normalize query string values to reduce metric cardinality. Converts numeric values like /page?id=123 to /page?id=NUMBER (#3665)

Fixes & improvements

• Fix issue on Azure ACI where tests that track many distinct metrics could fail or report incomplete results (#3662)
• Fix issue on AWS Fargate where --scenario-name flag was ignored, causing all scenarios to run instead of just the specified scenario (#3669)
• Upgrade to Playwright v1.57.0 (#3672)
• Routine dependency upgrades across all packages (#3675, #3609)

---

with contributions from @barth12 @JonathanSmithSkipton @manfromanotherland @hassy

Artillery v2.0.27

New features

Core

• Custom metric names are now limited to 1024 characters #3637

AWS ECS/Fargate

• Add new --no-assign-public-ip flag to disable automatic assignment of public IPs to worker tasks. This allows for load tests to run from private subnets with a NAT gateway attached for use-cases where traffic has to come from a set of known IPs. #3643

Azure ACI

• Azure load testing is now available on all subscriptions, including month-to-month ones. Previously only annual subscriptions could use the Azure integration.

Load testing with Playwright

• Upgrade to Playwright v1.56.1
• FID (First Input Delay) scores are no longer reported. FID has been deprecated as a Core Web Vital metric on September 9, 2024, and replaced by INP (Interaction To Next Paint). https://web.dev/articles/fid

Fixes & improvements

AWS ECS/Fargate

• Fix issue where ECS IAM policy could not be created #3640
• Fix handling of relative paths in config.payload when a separate config is used with the --config flag. #3657 #3653
• Fix handling of --scenario-name flag #3651

---

with contributions from @YH1715

Artillery v2.0.26

What's changed

New features

• Provide agetStash() method to access the Stash API from any Node.js script (#3624) (example)
• Provide type definitions for Playwright tests written in TypeScript (#3626) (example)

Fixes & improvements

• Fix: handle cases when the user does not have a default AWS region configured in their AWS config/profile (#3630)
• Fix: Check subscription plan correctly in Azure tests (#3623)
• Routine dependency upgrades for deprecation and security notices

Artillery v2.0.25

What's Changed

New features

• Stash API is now available. Stash API provides a persistent key-value store for use in your Artillery tests to share data between VUs, and offers Redis-compatible features like working with key-value pairs, lists, counters, and more. docs

Playwright

• Upgrade to Playwright v1.55.0 #3617

Fixes & Improvements

• Fix: Prioritize dependencies set via package.json over automatically-detected dependencies. This fixes issues where latest versions of dependencies could be installed rather than those specified in package.json #3616
• Fix: Avoid promisifying async "function" steps. This removes Node.js warnings when when an async function is used for a function step #3552
• Fix: Use China partition-aware ARNs and principals for tests on AWS Lambda/Fargate #3618
• Routine updates to dependencies to address security reports #3612
• Remove dependency on PostHog SDK #3615
• Migrate to AWS SDK v3. This is an internal change that does not affect any user-visible functionality