Unit testing is an essential part of software development that allows us to ensure the quality and reliability of our code. When working with services like AWS, it’s crucial to be able to fake the AWS API for efficient and reliable testing. In this blog post, we will explore the importance of unit testing and how to effectively mock the AWS API. Introduction It is not uncommon to see Lambda code with few or even zero unit tests.

If you have experience writing and deploying AWS Lambda functions in a non-strongly-typed language or if you have no experience with it at all, this article is for you. I’ll be explaining AWS Lambda from the basics up to developing using test-first methodologies such as TDD and deploying it. Note: I’ll be referring to AWS Lambda functions as just Lambda. What’s Lambda? Lambda is an event-based system that allows you to configure compute and networking resources to run code in some pre-defined runtimes.

The HTTP protocol is fast, secure, and reliable. However, it needs other protocols and services to work properly, and when things don’t go well it is necessary to have access to detailed information about the time spent in each step. The steps to make an HTTP call are as follows: DNS Lookup The client sends a DNS query to the DNS server. The DNS server responds with the IP for the name.