We aim to release a new version of Artillery Pro on every last Thursday of the month. Those monthly releases will contain new features and improvements to existing functionality, as well as fixes to lower priority bugs.
We aim to get high priority issues fixed as they become known, and will release patch-versions of Artillery Pro as those issues are fixed.
- Artillery workers will now use 1024 CPU units (equivalent to 1 vCPU) and 2048 memory units by default on both Fargate and classic ECS to improve performance
- Fixes an issue where the CLI would sometimes hang indefinitely due to getting into an inconsistent internal state because of Fargate taking too long to provision required containers
- The CLI will now provide progress updates as Fargate provisions the required resources (number of tasks ready / being provisioned / pending)
- Improvements to the accuracy of intermediate reports
- Improves Node v11 support
- Fix for cpu/memory overrides with
--launch-configsometimes not being set correctly when running on Fargate
- Fix for subscription limits sometimes not being applied correctly
- Activation with a Github account now requires the use of the
- Artillery Pro will now print a notification when an update is available
- Upgrade worker containers to use Node.js 10
- Various improvements to error handling & providing friendlier error messages
- Stability improvements for the installation/upgrade process of backend components
- Speed improvements in metric aggregation & reporting
- Serverless load testing with Fargate is here! To use Fargate, add a
--fargateflag, and tell Fargate which public subnets to use with
--public-subnet-ids, and your test will run from serverless Fargate containers rather than managed EC2 instances. Any existing Artillery test script, any scale, without having to manage any EC2 VMs.
- Fixed a bug which could cause
run-clusterto hang and never exit despite the test completing successfully.
- Various internal stability and performance improvements.
Important - Artillery Pro backend components need to be upgraded with
artillery setup-pro before using
- ECS worker containers can be customized now (with ECS container overrides for
environment) with --launch-config
DEBUGvariable may be set to customize debug output in CloudWatch logs for a test run
- Alpha AWS Fargate support (get in touch on email@example.com if you'd like to give it a go)
- Various internal improvements
- Autodetect plugins used in a test script and make them available in worker containers running on ECS
- Performance improvements
- File uploads:
setContentLengthHeaderoption may now be set
- Non-flat custom JS code dependencies are resolved properly now (for test scripts that load a custom JS module which loads other local modules in turn)