Discussion on "Cloud Integration Testing Made Easy: LocalStack + Testcontainers"

Anca G · 2023-06-14T12:09:15.036Z

Introduction LocalStack offers a compelling solution for streamlining the development and testing of your AWS-based applications. In a previous post, we explored the seamless transition between AWS and LocalStack, to ensure our application behaves th...

I am definitely in need of a similar approach to create integration tests for a solution using Lambda / S3 / SQS.

I eagerly pulled the code and am attempting run the integration tests but failing at the first hurdle - getting an error when the Spring Context test is running:

Error resolving attributes for queue update_shipment_picture_queue with strategy CREATE and queueAttributesNames []

oftware.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connection refused: no further information: localhost.localstack.cloud/127.0.0.1:4566

Unfortunately very new to using docker and integrating with AWS and unsure how to resolve - would you be able to provide any pointers?

Thanks

Great article. Really interesting. I've forked the repo and attempted compile the code, but hitting a compilation error using Java 17 LTS. Is this the latest code? Kind regards, David

Hi David, thanks for reading and giving feedback! It's been a while since the demo was created, and it definitively needs an upgrade. The Lambda function was using Java 11 (as it was the latest runtime supported at the time), while the rest of the project is using 17. I'll have a look; I'm sure some improvements are due. In the meantime, can you please tell me a bit more about when/how you're experiencing the error and what the message is?

Anca G Hi Anca, I updated the POM to that latest dependencies and that resolved a lot of errors (Lombok being the main one needing updating).

All of the ShipmentServiceIntegrationsTest PASS.

However, the tests for MessageReceiverIntegrationTest and LambdaIntegrationTest are failing. Various connection related errors, plus errors creating Lambda functions and invalid JSONObjects.

Some of the value placeholders are not getting replaced correctly and then failing.

For example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'amazonS3Config': Injection of autowired dependencies failed

and

Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'aws.credentials.access-key' in value "${aws.credentials.access-key}"

Search Hashnode

Cloud Integration Testing Made Easy: LocalStack + Testcontainers

Responses2