Maintenance: add e2e tests for Batch Processing

[dreamorosi]

Summary

Following the v2.26.0 release we introduced a regression that couldn't be detected in unit tests and existing e2e tests.

Because of this, we should add isolated and dedicated test cases for the Batch Processing utility.

Why is this needed?

So that we can increase the confidence that new code in this utility stays backwards compatible and with less chances of regressions.

Which area does this relate to?

Other

Solution

No response

Acknowledgment

• [x] This request meets Powertools for AWS Lambda (TypeScript) Tenets
• [ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

I'm going to be adding the Batch Processing utility to the e2e test matrix here and add two test cases:

• one SQS queue triggering a Lambda function using Batch Processing alone
• one SQS queue triggering a Lambda function using Batch Processing together with Parser

The first one will catch regressions similar to the one we introduced in the previous release since it's testing the module in isolation while the second should detect regressions related to the integration between the two or specifically related to Parser being used with Batch Processing.