Releases: aws-solutions/distributed-load-testing-on-aws
Releases · aws-solutions/distributed-load-testing-on-aws
v3.2.1
[3.2.1] - 2023-04-17
Fixed
- Add ownership parameter to S3 logging bucket to account for changes in S3 default behavior.
v3.2.0
[3.2.0] - 2023-03-09
Added
- Task limits based on on-demand vCPU quotas for the account along with currently running Fargate tasks.
- Table to the console when creating a test to visualize available Fargate quotas.
- Auto-refresh functionality
- eslint and prettier formatting
Fixed
- Bug fix for #115 where Step Functions hits a task execution limit.
- Bug fix for #115 where test does not cancel properly.
- CloudWatch Dashboards link in console
- Deletion of CloudWatch Dashboards on test deletion
Security
- Updated to bootstrap 5
- Updated to blazemeter/taurus version 1.16.9
v3.1.1
v3.1.0
[3.1.0] - 2022-11-10
Added
- Added AppRegistryAWS Service Catalog AppRegistry support for all deployments of the solution.
- Due to current limitations of AppRegistry, a separate instance of AppRegistry is launched for each region that this solution is deployed to.
v3.0.0
[3.0.0] - 2022-08-24
⚠ BREAKING CHANGES
Version 3.0.0 does not support upgrading from previous versions.
Added
- Merge #71 by @pyranja
- Multi-region load test support
- Template for secondary regions
- Menu option for region management
- Region selection in test creation
- Results viewable by region
- Real time data on UI for running tests
- Upload bzt log, as well as jmeter log, out, and err logs to S3
- Link to S3 test results in the test details
- Logging for failed tasks
Changed
- History moved to separate table
- History view moved to modal rather than separate link
- Updated to CDK V2
Fixed
- Bug fix for long running containers by adding timeout to sockets
- Bug fix port issues by handing SIGTERM properly
- Bug fix for graceful failure when leader task fails
- Bug fix for tasks which launched but failed to provision
Removed
- Sleep between runTask API calls
v2.0.2
[2.0.2] - 2022-03-31
Added
- Enabled encryption in transit for the logging S3 bucket.
v2.0.1
[2.0.1] - 2021-12-13
Version 2.0.1 supports upgrading from version 2.0.0 but not from version 1.3.0 and below
Note: When upgrading from version 2.0.0 to 2.0.1, make sure to clear CloudFront and browser cache to avoid image issues.
Changed
- Updated AWS SDK version in development dependencies for AWS Lambda functions
- Bug fix to resolve issue with displaying a large number of tests
- Bug fix for error finalResults function error ValidationException: Item size to update has exceeded the maximum allowed size
- Merge #64 from @rmdashrfslash
v2.0.0
[2.0.0] - 2021-09-30
⚠ BREAKING CHANGES
Version 2.0.0 does not support upgrading from previous versions.
Added
- Support to view complete data from previous test runs, including test configuration, test data, and Amazon CloudWatch dashboards
- Results History now has a
View details
link to display data from previous test runs
- Results History now has a
- Support for an existing Amazon VPC
- Launch Fargate tasks in multiple availability zones
- Using AWS CDK source code to generate the AWS CloudFormation template
Changed
- Results History displays:
- Run Time
- Task Count
- Concurrency
- Average Response Time
- Success %
- Tags created in CloudFormation propagated to Fargate test tasks
- Test ids only contain alphanumeric characters
Removed
- Remove AWS CodePipeline, AWS CodeBuild, and Amazon ECR image repository resource creation by AWS CloudFormation stack
- The solution's container image is stored in a public ECR image repository managed by AWS
- Remove
ECRChecker
lambda function and state machine stage
Release v1.3.0
[1.3.0] - 2021-04-30
Added
- Support for up to 1000 tasks
- Added TaskCanceler lambda to cancel tasks
- Added steps in step function to support launching 1000 tasks
- Added StartedBy tag to tasks for use by task listing functions
- Modified all ECS task listing functions to support listing 1000 tasks
- Modified TaskRunning lambda function to support being called multiple times from step functions
- Tests start simultaneously
- Added ecscontroller.py to container package
- Added ecslistener.py to container package
- TaskRunner lambda launches worker tasks first, then leader task once workers are running
- Run tests concurrently
- Removed disabling of submit buttons if there is a test running
- Unbuffered bzt output and added test Id to CloudWatch logs for access to test specific logs
- Added support for Docker Hub login
- Added Secrets manager parameter to include secret containing Docker Hub credentials
- Included more metrics
- Added virtual users, failures, and successes to graph
- Added individual CloudWatch dashboards and widget for each metric for real time results
- Added support for scheduling tests
- Added scheduling options to form
- Added scheduled CloudWatch rules to start tests on schedule
- Added next run and recurrence to dashboard page in UI
- Added recurrence to details page in UI
- Added SolutionId and TestId tag to Fargate tasks and SolutionId tag to API Gateway
Changed
- Merge #50 by @naxxster
- Increased Task Count limits
- Changed ETA for running tasks to be dynamic based on number of tasks
- Increased task cpu and memory to handle increased cpu load
- Package versions
- Improved unit tests
- UI changes
- Changed update button to edit in details page
- Changed submit button to "Run Now" or "Schedule" in create page
- Changed details URL to include test id
- Changed concurrency message to provide guidelines to determine max concurrency
Removed
- Concurrency Limits
- Removed aggregated CloudWatch dashboard and metric
Version 1.2.0
Added
- JMeter input file support and plugins support
- JMeter input files should be zipped with the JMeter script file.
- Add
jetty-*.jar
files to the Amazon ECR to support JMeter HTTP/2 plugin:
- UI Detail page
- Sub test results by labels
- Requests per second
- Complete task counts
- Check if Amazon ECR is ready before running the test
- More error handlings in AWS Step Functions
- If any error happens in any steps, the Lambda function updates the test status to
FAILED
. - If any AWS Fargate tasks are possibly hanged forever, the
task-status-checker
Lambda function stops the tasks. - When there is no result in the S3 bucket, it regards the result as
FAILED
.
- If any error happens in any steps, the Lambda function updates the test status to