Serverless Testing - AWS Lambda



Let's start with what is Serverless Framework?

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster.

The Serverless Framework helps you develop and deploy your AWS Lambda functions, along with the AWS infrastructure resources they require. It's a CLI that offers structure, automation and best practices out-of-the-box, allowing you to focus on building sophisticated, event-driven, serverless architectures, comprised of Functions and Events.
  • It manages your code as well as your infrastructure
  • It supports multiple languages (Node.js, Python, Java, and more)
AWS Lambda is a compute service that lets you run code without provisioning or managing servers. You can also build serverless applications composed of functions that are triggered by events and automatically deploy them using AWS CodePipeline and AWS CodeBuild.

The Mantra is: Build auto-scaling, pay-per-execution, event-driven apps on AWS Lambda

While the Serverless Architecture introduces a lot of simplicity when it comes to serving business logic, some of its characteristics present challenges for testing. They are:
  1. The Serverless Architecture is an integration of separate, distributed services, which must be tested both independently, and together.
  2. The Serverless Architecture is dependent on internet/cloud services, which are hard to emulate locally.
  3. The Serverless Architecture can feature event-driven, asynchronous workflows, which are hard to emulate entirely.

To get through these challenges, and to keep the test pyramid in mind, keep the following principles in mind:
  1. Write your business logic so that it is separate from your FaaS provider (e.g., AWS Lambda), to keep it provider-independent, reusable and more easily testable.
  2. When your business logic is written separately from the FaaS provider, you can write traditional Unit Tests to ensure it is working properly.
  3. Write Integration Tests to verify integrations with other services are working correctly.
From an AWS book the three levels of testing for a serverless architecture:
  • Acceptance – does the whole system work?
  • Integration – does our code work against code we can’t change?
  • Unit – do our objects do the right thing, are they easy to work with?
  • A Lambda function is ultimately a piece of code that AWS invokes on your behalf when some input event occurs. To test that it integrates correctly with downstream systems you can invoke the function from your chosen test framework

Source: http://theburningmonk.com/2017/02/yubls-road-to-serverless-architecture-part-2/
https://read.acloud.guru/testing-and-the-serverless-approach-495cef7495ea
https://martinfowler.com/articles/microservice-testing/
https://martinfowler.com/articles/serverless.html
https://aws.amazon.com/blogs/compute/serverless-testing-with-aws-lambda/

Comments

  1. Unknown24/10/18

    nice post! Thanks for delivering a good stuff related to DevOps, Explination is good, nice Article
    anyone want to learn advance devops tools or devops online training
    DevOps Online Training
    DevOps Training institute in Ameerpet

    ReplyDelete
  2. Anonymous13/6/19

    This comment has been removed by the author.

    ReplyDelete
  3. Donald marshal31/3/20

    Nice Blog very use full inormation.AWS-certified experts help you develop a cloud strategy which aligns with your business transformation road map and implement cloud management solutions to harness the AWS Cloud Managed Services

    ReplyDelete
  4. Balajee Nanduri8/5/20

    Nice post. Keep updating AWS Online Training

    ReplyDelete
  5. KITS Technologies16/10/21

    I really liked your blog post.Much thanks again. Awesome.
    aws training
    r programming training

    ReplyDelete

Post a Comment

Popular posts from this blog

Software Testing @ Microsoft

Image
In continuation from my previous  series of posts  targeting testing in top few companies from the technology space. After  Software Testing @Facebook  and @Google  we shall now look at Microsoft: Testing@Microsoft Software Development Engineers in Test (SDETs) are usually just called Test and sometimes Software Testing. SDETs are responsible for maintaining high testing and qualityassurance standards for all Microsoft products. Software Development Engineers (SDEs) are often referred to as Software Development. SDEs write the code that drives Microsoft products and upgrades. Very few teams in Microsoft are still using SDETs to do significant amount of manual testing. Manual testing is mainly outsourced. Actually, as early as in 2004, for example, most of the manual testing of MSN Explorer was outsourced. Think about it this way: it just doesn't make sense for test manager to spend their headcount (SDETs) on something can be easily outsourced.  Until 2005, Microso
Read more

Trim / Remove spaces in Xpath?

Image
If you are wondering how you can trim the spaces in your xpath, this is how: The normalize-space function strips leading and trailing white-space from a string, replaces sequences of white-space characters by a single space, and returns the resulting string. Example : Which one is better? //td[starts-with(normalize-space(),'Text to Trim')] //td[starts-with(normalize-space(text()),' Text to Trim ')] The second option is better as it targets at the specific nodes More string functions in XPATH: Functions Description starts-with( string1 ,  string2 ) Returns true if the first string starts with the second string. contains( string1 ,  string2 ) Returns true if the first string contains the second string. substring( string offset length ) Returns a section of the string. The section starts at  offset (which is a number), and is as long as the value provided at  length. substring-before( string1 ,  string2 ) Returns the part of  string1  up unti
Read more