Maintenance: migrate Batch Processing unit tests to vitest

[dreamorosi]

Summary

In #2935 we have added Vitest to the workspace, as part of this effort we should move the Batch Processing unit tests to use it.

The activity should be considered complete once the tests can be run: in 1/ CI environment, 2/ locally as a workspace, 3/ locally as standalone package, and 4/ locally in the pre-push commit hook.

As part of this work, we should also disable default coverage reporting.

Why is this needed?

So that we can continue the migration to Vitest.

Which area does this relate to?

Tests

Solution

No response

Acknowledgment

• 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.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.