Maintenance: filter e2e tests in pre-push hook

[dreamorosi]

Summary

We use pre-push hooks to run quick tests on the code and give fast feedback to contributors. With the ongoing migration to vitest, we have added a vitest command to the hook, however in doing so we forgot to filter the tests. This causes both unit and e2e tests to run before each commit.

Why is this needed?

We should apply a filter and run only unit tests, so that we don't slow down the commit workflow too much. These tests will be run on the CI anyway.

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

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

[github-actions]

This is now released under v2.10.0 version!