All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Enabled encryption in transit for the logging S3 bucket.
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.
- 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
⚠ BREAKING CHANGES Version 2.0.0 does not support upgrading from previous versions.
- 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
- 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
- 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
- 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
- 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
- Concurrency Limits
- Removed aggregated CloudWatch dashboard and metric
- 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
- Use
Promise.all()
inresults-parser
to improve the performance - Correct average bandwidth on the Detail page
- Packages version
- Fix occasional wrong test duration time on the report
- Dashboard order by
Last Run (UTC)
- Maximum upload file size to 50MB to support JMeter input files
- JMeter support with
jmx
script: #3 - Add
START
button on details page - Add
CANCEL
button on create page - Add AWS Step Functions to run tasks and update result instead of Amazon DynamoDB and Amazon SQS
- Add
BucketEncryption
forConsoleBucket
- Add API Gateway logging
- Merge #15 by @afittz
- Merge #16 by @Patrick-56Bit
- Change
LAST RAN
toSTARTED AT
and addENDED AT
information when test is completed - Change CodeBuild image to
aws/codebuild/standard:4.0
- Update Node.js version from 10.x to 12.x
- All Amazon S3 buckets do not allow public access.
- Amazon SQS queue
- Amazon DynamoDB Results table
- CHANGELOG version 1.0.0 release