Cloud Integration Testing Made easy with LocalStack and Testcontainers (Ghent)

Slide 1

Slide 1 text

Cloud Integration Testing Made easy with LocalStack and Testcontainers Ghent 06.02.2024 localstack.cloud

Slide 2

Slide 2 text

Anca Ghenade - Developer Advocate - anca.ghenade@localstack.cloud @tinyg210

Slide 3

Slide 3 text

Testing…

Slide 4

Slide 4 text

Some things cannot just easily be tested, for example plane sensors. Landing gear sensors to be more precise.

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

So what’s the ﬁrst thing we take away from this? Testing must be realistic.

Slide 7

Slide 7 text

But how realistic?

Slide 8

Slide 8 text

The truth is we’ve gotten very used to being “fake”. ● Test data → a runner that cleans a database on every test run. We get green tests with migration problems. ● Selenium → a fake user, using a mouse and keyboard, over and over again. We assume it’s realistic. ● Stamina → the runtime is always fresh for tests. What about subtle memory leaks? ● Scaling → tests run against a single process web server. Reality: a multi-thread environment.

Slide 9

Slide 9 text

Sometimes you have no choice.

Slide 10

Slide 10 text

WE INTERRUPT THE REGULAR SCHEDULED PRESENTATION TO BRING YOU THIS IMPORTANT STORY TIME

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

What about applications with dependencies in the cloud?

Slide 13

Slide 13 text

We want to keep it as real as possible when we’re testing our AWS-powered applications and the interaction between various components.

Slide 14

Slide 14 text

The reality: (of using a real cloud environment)

Slide 15

Slide 15 text

Environment Setup: - AWS Account: Ensure you have access to an AWS account for testing purposes. - Separate Test Environment: Create a separate AWS environment for integration testing to avoid aﬀecting your production environment. - Use of AWS Services: Set up the AWS services you need for testing (databases, storage buckets, queues, Lambda functions, etc). Test Data Preparation: - Data Generation: Prepare test data to use during your integration tests. This data should mimic real-world scenarios and cover diﬀerent use cases. - Data Isolation: Isolate test data from production data to prevent accidental data loss or corruption.

Slide 16

Slide 16 text

Automate Integration Tests: - Write integration tests using test automation frameworks such as JUnit, TestNG, or a tool speciﬁc to your programming language or AWS services (e.g., AWS SDK for Java, AWS CDK). - Use testing libraries that support AWS services to interact with your resources programmatically (e.g., AWS SDKs, AWS Amplify, AWS CDK constructs). - Perform tests that exercise interactions between AWS services, such as Lambda functions invoking other services, S3 bucket operations, or SQS queue processing. Test Scenarios: - Test various scenarios, including both positive and negative cases. Ensure that your tests cover diﬀerent service interactions, error handling, and edge cases.

Slide 17

Slide 17 text

Service Isolation: - Isolate AWS services as needed to ensure that your tests do not interfere with each other or the production environment. This can involve using separate AWS accounts or resource tagging. Testing AWS Lambda Functions: - Test AWS Lambda functions locally using a local development environment or tools like the AWS SAM CLI. - Automate the deployment and invocation of Lambda functions during testing.

Slide 18

Slide 18 text

Security Testing: - Include security testing in your integration tests to identify vulnerabilities and ensure that AWS security conﬁgurations are correct. - Test IAM roles, security groups, and network conﬁgurations. Cleanup and Resource Management: - Implement resource cleanup procedures to ensure that resources created during testing are properly disposed of to avoid unnecessary costs and resource leakage. Continuous Integration (CI): - Integrate integration tests into your CI/CD pipeline to ensure that tests are executed automatically whenever code changes are pushed.

Slide 19

Slide 19 text

Documentation and Reporting: - Document test scenarios, results, and any issues encountered during integration testing. - Use reporting and visualization tools to present test results in a clear and actionable format. Regression Testing: Periodically rerun integration tests to catch regressions as you make changes or updates to your AWS infrastructure and application code.

Slide 20

Slide 20 text

So things are kind of… complicated. 󰤆

Slide 21

Slide 21 text

What are some of the common approaches to testing with cloud dependencies?

Slide 22

Slide 22 text

The “let’s prove it works”

Slide 23

Slide 23 text

Focus on: ● Mostly end-to-end and integration testing ● Mocking only the necessities

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

The “mocking the boundaries”

Slide 26

Slide 26 text

Focus on: ● Mock/fake remote systems ● Mostly unit and end-to-end testing

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

Circling back to reality… reality is expensive, so we also want to test on a budget.

Slide 29

Slide 29 text

Mocking carries the risk of not getting updated and if we mock everything, aren’t we just making sure that the mocks work as expected?

Slide 30

Slide 30 text

And how can we bring the ease and speed of unit tests into our integration tests?

Slide 31

Slide 31 text

What is LocalStack and how can it help you? A fully functional local cloud stack that was born out of these exact concerns.

Slide 32

Slide 32 text

● Enables a highly eﬃcient dev & test loop for cloud apps ● Ships as a Docker image, easy to install and start up ● Support for 90-ish services (and growing): ○ compute (Lambda, ECS, EKS) ○ various databases (DynamoDB, RDS) ○ messaging (SQS, Kinesis, MSK) ○ some sophisticated/exotic APIs (Athena, Glue) ● CI integrations & advanced collaboration features ● Branching out into other areas: Chaos Engineering, IAM Security Testing, Cloud Ephemeral Environments, 3rd Party Extensions, etc

Slide 33

Slide 33 text

How much of your system you can test Cloud emulation Staging environments Real AWS Mocking So how much reality can we have in cloud application testing? 3 4 Service emulation 2 1

Slide 34

Slide 34 text

https://github.com/tinyg210/opentofu-shipment-list-demo

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

Using Spring Proﬁles…

Slide 37

Slide 37 text

Scenario 1 (Production) Scenario 2 (Development)

Slide 38

Slide 38 text

Scenario 1 Scenario 2

Slide 39

Slide 39 text

What about integration tests?

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

What approach do we use for testing our apps?

Slide 43

Slide 43 text

1. The “my app changes frequently” example

Slide 44

Slide 44 text

Testing your application workﬂow

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

And your app runs against LocalStack.

Slide 47

Slide 47 text

2. The “my app is pretty much ready” example Source: https://github.com/tinyg210/stack-bytes-apigw-lambda-s3 Folder: github-actions-testcontainers

Slide 48

Slide 48 text

Test successful POST Test successful GET Test fails validation on incorrect values Test 404 on wrong param

Slide 49

Slide 49 text

Your tests will revolve around an HTTP client

Slide 50

Slide 50 text

And your app runs inside LocalStack.

Slide 51

Slide 51 text

There are several ways to provision your infrastructure for testing.

Slide 52

Slide 52 text

1. You do everything yourself. (example: https://github.com/tinyg210/testcontainers-shipment-list-demo)

Slide 53

Slide 53 text

2. You use AWS CLI scripts via init hooks. (example: https://github.com/tinyg210/stack-bytes-apigw-lambda-s3)

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

3. Use LocalStack Cloud Pods (https://github.com/tinyg210/testcontainers-shipment-list-cloud-pods)

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

4. Use a mix of all of the above. - spin up only desired services at startup - manage other resources via SDK clients

Slide 58

Slide 58 text

What about CI?

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

Your local tests…

Slide 61

Slide 61 text

In CI…

Slide 62

Slide 62 text

Some Tips and Tricks

Slide 63

Slide 63 text

Use a waiter to make sure your Lambdas are in state ACTIVE and not just created.

Slide 64

Slide 64 text

Source: https://aws.amazon.com/blogs/compute/coming-soon-expansion-of-aws-lambda-states-to-all-functions/

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

Use this nifty conﬁguration to scan the LocalStack logs and make sure your instance is in the right state before the tests are allowed to start: