v2.0.0-26

New features

• Artillery will now print the contents of the test bundle created for tests running on AWS Lambda
  

Fixes and improvements

• Fix issue with installing dependencies when running on AWS Lambda
• Fix issue with printing error logs from AWS Lambda workers

v2.0.0-25

New features

AWS Lambda support

• Test scripts using custom JS code (in config.processor), CSV files, and external config files (used with the --config flag) can now run on Lambda
• Cost estimations for each test are now reported at the end of each test run
  
• nodejs16.x runtime will be used by the Lambdas

Fixes and improvements

• Always resolve path to processor relative to the config file when a separate config file is used via the --config flag
• Better handling of errors in worker Lambdas

v2.0.0-24

New features

• Cookie parsing behavior may be customized via config.http.cookieJarOptions by passing options to the underlying ToughCookie instance (docs)

Fixes & Improvements

• More predictable rampTo behavior when using smaller values of arrivalRate/rampTo with a large duration (#1621)
• maxVusers setting is applied correctly when running on multiple CPU cores
• AWS Lambda functions will always use the latest release of Artillery

Contributors: @juanig1 @hassy

v2.0.0-23

New features

• Add cdnHit expectation to expect plugin to check that the response was served from cache by a CDN
• Add support for providing a CA certificate to use with Prometheus Pushgateway in publish-metrics plugin

Fixes & Improvements

• Handle malformed cookies from HTTP services (#1540)
• Fix crashes that could be caused by redirect chains in combination with capture/afterResponse hooks (#1544 #1568)
• Make sure response body is available to afterResponse hooks when the response is compressed (#1563)
• Add support for JSON-LD in the expect plugin (artilleryio/artillery-plugin-expect#34)
• Make sure metrics sent to Prometheus Pushgateway with publish-metrics are flushed before Artillery exits
• Routine dependency upgrades to address security advisories

Contributors: @juanig1, @luneo7, @MaximeTaqt, @hassy

v2.0.0-22

Fixes & Improvements

• Improve error handling on AWS Lambda
• Fix issue which could cause errors when handling HTTP redirects
• Fix issue with cookies not being saved and reused under some conditions
• Various maintenance & security dependency updates

v2.0.0-21

New features

This release adds support for distributed cloud-native testing with AWS Lambda out of the box.

This feature is to be considered experimental at the moment. Please report bugs in Issues.

The --platform and --platform-opt flags have been added to the run command.

To run a test on AWS Lambda in the us-east-1 region, with 100 parallel Lambda workers, run:

artillery run --platform aws:lambda --platform-opt region=us-east-1 my-script.yml

This requires an AWS profile configured locally.

v2.0.0-20

Fixes & Improvements

• Allow think, count and timeout properties to be numbers or strings
• Allow zero duration think steps
• Dependency updates (async, got, socket.io-client, oclif, etc)

v2.0.0-19

New

• Add support for loading environment variables from a dotenv file with --dotenv (#1478)
• Add loadAll option to make all CSV data available to each VU (#1485)
• New & improved HTML reports

v2.0.0-18

• Fix: retain histograms field in JSON reports for backwards-compatibility
• Replace deep-equal with fast-deep-equal (ty @toastal)

v2.0.0-17

• Node.js v16+ is now recommended
• Upgrade Docker image to Node v16 LTS
• Fix a bug with rampTo under certain conditions (#1443) (@GeekyDeaks)
• Include artillery-plugin-ensure (#1457)