Introducing Harness Testing

[darklight3it]

📬 Issue #, if available:

N/A

✍️ Description of changes:

This PR adds Docker-based testing infrastructure using AWS's containerized-test-runner-for-aws-lambda, enabling automated testing of Lambda functions in a containerized environment that closely mirrors the AWS Lambda execution environment.

The PR introduces a test-dockerized Makefile target that runs test suites defined in test/dockerized/*.json files. These test suites specify handlers to test (from the examples directory), request payloads, and expected response assertions with optional jq transforms for validation.

The infrastructure reuses Lambda binaries from the /examples folder as test handlers, demonstrating the concept with an initial test case for basic-lambda. Additional tests and multi-concurrency scenarios can be added by creating new test suite JSON files.

A GitHub Actions workflow provides CI/CD integration for automated testing on pull requests.

Testing

Run dockerized tests locally:

make test-dockerized

Run RIE tests:

make test-rie
HANDLERS_TO_BUILD="basic-lambda basic-sqs" make test-rie

Build specific examples:

EXAMPLES="basic-lambda basic-lambda-concurrent" make build-examples

🔏 By submitting this pull request

• I confirm that I've ran cargo +nightly fmt.
• I confirm that I've ran cargo clippy --fix.
• I confirm that I've made a best effort attempt to update all relevant documentation.
• I confirm that my contribution is made under the terms of the Apache 2.0 license.on.
• I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jlizen]

Does this action exist? The ci is failing to find it, and I don't see references elsewhere on the Internet.

I wonder if the existing test-rie workflow is close to what you want here, and could be adapted?

Seems like the main thing missing would be a small script to translate the request mappings into curl requests that assert against the response? Along with some parameterizing to feed in the proper lambda binary and test assets to the dockerfile?

[jlizen]

(I like what you are trying to do here with the testing harness though, seems super handy... If the referenced action is in development / not yet public... Excited to see it!)

[darklight3it]

Sorry 😢 for this you miss some context here, and I had no time to write this in the appropriate channel. This stuff is agreed with @maxday.

That action is already used in the ruby repo and Maxime is actively working in making it public. The idea is to use the same harness test framework in all lambda runtimes.

I created a CR on that repo and this one is dependent on that to be working.

[darklight3it]

BTW I think the existing test-rie way of dealing with those tests will be removed in favor how the harness test standard that easily allow you to make assertions on the lambda response.