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

06.02.2024 Cloud Integration Testing Made easy with LocalStack and Testcontainers - 50min talk at Config Management Camp, Ghent

Transcript

1. Cloud Integration Testing Made easy with LocalStack and Testcontainers Ghent 06.02.2024 localstack.cloud
2. Anca Ghenade - Developer Advocate - anca.ghenade@localstack.cloud @tinyg210
3. Testing…
4. Some things cannot just easily be tested, for example plane sensors. Landing gear sensors to be more precise.
6. So what’s the first thing we take away from this? Testing must be realistic.
7. But how realistic?
8. 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.
9. Sometimes you have no choice.
10. WE INTERRUPT THE REGULAR SCHEDULED PRESENTATION TO BRING YOU THIS IMPORTANT STORY TIME
12. What about applications with dependencies in the cloud?
13. We want to keep it as real as possible when we’re testing our AWS-powered applications and the interaction between various components.
14. The reality: (of using a real cloud environment)
15. 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 affecting 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 different use cases. - Data Isolation: Isolate test data from production data to prevent accidental data loss or corruption.
16. Automate Integration Tests: - Write integration tests using test automation frameworks such as JUnit, TestNG, or a tool specific 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 different service interactions, error handling, and edge cases.
17. 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.
18. Security Testing: - Include security testing in your integration tests to identify vulnerabilities and ensure that AWS security configurations are correct. - Test IAM roles, security groups, and network configurations. 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.
19. 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.
20. So things are kind of… complicated. 󰤆
21. What are some of the common approaches to testing with cloud dependencies?
22. The “let’s prove it works”
23. Focus on: • Mostly end-to-end and integration testing • Mocking only the necessities
25. The “mocking the boundaries”
26. Focus on: • Mock/fake remote systems • Mostly unit and end-to-end testing
28. Circling back to reality… reality is expensive, so we also want to test on a budget.
29. 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?
30. And how can we bring the ease and speed of unit tests into our integration tests?
31. What is LocalStack and how can it help you? A fully functional local cloud stack that was born out of these exact concerns.
32. • Enables a highly efficient 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
33. 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
34. https://github.com/tinyg210/opentofu-shipment-list-demo
36. Using Spring Profiles…
37. Scenario 1 (Production) Scenario 2 (Development)
38. Scenario 1 Scenario 2
39. What about integration tests?
42. What approach do we use for testing our apps?
43. 1. The “my app changes frequently” example
44. Testing your application workflow
46. And your app runs against LocalStack.
47. 2. The “my app is pretty much ready” example Source: https://github.com/tinyg210/stack-bytes-apigw-lambda-s3 Folder: github-actions-testcontainers
48. Test successful POST Test successful GET Test fails validation on incorrect values Test 404 on wrong param
49. Your tests will revolve around an HTTP client
50. And your app runs inside LocalStack.
51. There are several ways to provision your infrastructure for testing.
52. 1. You do everything yourself. (example: https://github.com/tinyg210/testcontainers-shipment-list-demo)
53. 2. You use AWS CLI scripts via init hooks. (example: https://github.com/tinyg210/stack-bytes-apigw-lambda-s3)
55. 3. Use LocalStack Cloud Pods (https://github.com/tinyg210/testcontainers-shipment-list-cloud-pods)
57. 4. Use a mix of all of the above. - spin up only desired services at startup - manage other resources via SDK clients
58. What about CI?
60. Your local tests…
61. In CI…
62. Some Tips and Tricks
63. Use a waiter to make sure your Lambdas are in state ACTIVE and not just created.
64. Source: https://aws.amazon.com/blogs/compute/coming-soon-expansion-of-aws-lambda-states-to-all-functions/
66. Use this nifty configuration to scan the LocalStack logs and make sure your instance is in the right state before the tests are allowed to start:
68. Streaming container output to an SLF4J logger
70. Lastly, here’s a workaround to shut down your Lambda containers
73. Thank You!