parallel action for making parallel requests in HTTP tests--quiet flag - docseu-north-1 to supported regions--quiet flag - docs1.43.1 - docsreplaceSpanNameRegex config option - DocssampleRate tracing option setplugins.publish-metrics.spans.exported ) when tracing is enabledARTILLERY_CLOUD_API_KEY environment variable from being picked up by Fargate when using --dotenvETIMEOUT or ECONNRESET - docsasync functions as hooks - docs--launch-config flagexpect from @playwright/test work natively with Typescript support - Documentationtarget as Playwright’s baseURL by default, allowing test scripts to include only relative paths in page navigations (e.g. page.goto('/docs') ) - Documentationconfig.bundling.external to set packages that can’t be bundled as external - Documentation{{ $testId }} in scenarios/config and vuContext.vars.$testId in custom codeopentelemetry reporter with a test_id attribute, making it easier to search for all relevant data from a particular test runArtillery will now aim to release a new CLI version every first and third Monday of each month, when possible.
testIdAttribute setting - Documentationheadless mode by default when running in Fargate, as headed mode is not compatible with Fargate--spot flag - Documentation$randomString(length) utility to return correct number of characters and allow length larger than 10eu-west-2, eu-west-3, us-east-2, us-west-2, ca-central-1, ap-east-1, ap-northeast-2, ap-southeast-1, ap-southeast-2, ap-northeast-1, me-south-1, sa-east-1 )--variables flag in run-fargate command - Documentation--region flagbrowser.page.codes.<code> metric - Documentationbefore/ after hooks that prevented the Playwright engine from working - Documentationtest.step() with OpenTelemetry Playwright tracing enabledthink steps in scenariosmetrics-by-endpoint plugin is now enabled by default to capture per-URL metrics in HTTP tests. The metrics will be available only in the JSON report and not output to the console, unless the plugin is loaded explicitly by the user.--cpu and --memory flags$env not resolving correctly in the config section--scenario-name not picking up the correct scenariofake-data plugin to allow for realistic test data to be generated in your tests - docsensure checksexpect plugintest.step() calls, page navigation events, and Core Web Vitals metrics400 or higherHTTP_REQUEST_CONTENT_LENGTH, HTTP_USER_AGENT and HTTP_FLAVOR attributesvu.uuid) not always being set correctlypublish-metrics pluginFID Core Web Vital metric not being emitted as expected--cpu and --memory flagsargs/on optionsmatch errors in the reportplaywright: Update Playwright version to latest (1.39.0).playwright: Add a convenience test.step() helper, allowing you to break your tests into steps that emit custom timing metrics - Docs.--scenario-name, allowing you to specify which scenario to run by its name in the test script - Docs.mean as a metric.context.scenario - Docs.
socketio: Allow nested options (e.g. namespace) in emit without throwing validation error - Docs.socketio: Allow emit action to be an array of strings - Docs.fargate: Fix issue with --packages flag.fargate: Include apdex plugin and playwright engine by default in image, preventing additional installation in workers.capture.config.engine.apdex - Allow frustrated, satisfied and tolerated metrics to be checked with ensure plugin.apdex - Prevent plugin from crashing when using processor functions.publish-metrics - Set headers as metadata for otel-grpc exporter in OpenTelemetry reporter - Docs.publish-metrics - Create endpoint path correctly so it works with managed instances of Dynatrace.publish-metrics: Fix OpenTelemetry reporter debug logging.publish-metrics plugin can now be configured to send Artillery metrics and events to Dynatrace. Read more in the docsconfig.http.defaults - default headers and cookies for all requests in a test may now be set via config.http.defaults--variables to be used anywhere in configpublish-metrics - Exit early if required config is missing for publish-metricspublish-metrics - Reduce memory usage of the pluginexpect - add useRequestNamesOnly optionensure - fix bug where ensure config under config.plugins.ensure would not get picked up
The load test summary view will now calculate and display Apdex scores for load tests that make use the built-in apdex plugin.
Apdex (Application Performance Index) is an open standard for measuring performance of HTTP services. The Apdex score converts response times into a single score that reflects user satisfaction with the service.
This release adds support for running tests on AWS Fargate. Scale out your load tests horizontally from any of the six supported regions.
artillery run-fargate --count 10 --region us-east-1 my-script.yml
Supported regions:
us-east-1us-west-1eu-west-1eu-central-1ap-south-1ap-northeast-1AWS Fargate is a serverless solution that requires no infrastructure to be managed, and unlike AWS Lambda does not impose a restriction on the duration of your load tests.
Artillery’s Playwright integration is fully supported on Fargate, to let you run browser-based load tests at scale with ease.
Playwright support is now built into Artillery. The integration in artillery-engine-playwright is now bundled into the Artillery CLI.
testFunction attribute rather than flowFunctionflow attribute may now be omitted in Playwright engine scenarioslambdaRoleArn to AWS Lambda engine correctlyhttp.downloaded_bytes metric$env variable (the current way of accessing those via $processEnvironment is still supported but will be deprecated in future)
config.plugins and engines loaded via config.enginesnotStatusCode check in the expect pluginincludeOnly and excluded options may be used to configure the list of Artillery metrics which will be sent to Datadogartillery run is used with the --output option, Artillery will check if destination exists before running the test
We have released Artillery v2.0.0-28, which adds support for AWS CloudWatch, and features a number of performance and stability improvements.
artilleryio-default-lambda-role role, you will need to re-attach it to the new artilleryio-default-lambda-role-20230116 roleprobe command has been removed from the CLI. The functionality has been moved to the new Skytrace CLIgzip) will be decompressed by default now. (Set gzip: false to disable automatic decompression if required to improve performance.)arrivalRate and rampTo set to 0rampTo logic to result in more predictable and deterministic rampsmaxVusers setting that would lead to unexpected number of VUs to be generatedartillery objectmemory-size and security-group-ids options
We have improved the layout and styling of reports generated with artillery report.
You can now load environment variables from a file with the --dotenv flag. Those env vars are available in Artillery scenarios through the $env variable.
We released an official AWS CDK-based installer for Artillery dashboard.
The dashboard can now be deployed in more than one way to fit the exact requirements of your organization:
We added support for authentication through GitHub.
We have launched the first version of Artillery Probe, a smart and user-friendly HTTP client built into Artillery
Artillery Probe is available in the most recent release of Artillery:
npm install -g artillery@latest
wait action to WebSocket scenariosDetailed changelog for the CLI on GitHub releases page.
