Maintenance: vitest coverage misreporting

[dreamorosi]

Summary

While working on #3133, @arnabrahman reported that the test coverage within packages that have been migrated to vitest varies depending on how you run the test command.

We should look into the issue and understand why it's happening and how to fix it. See here for more details.

Why is this needed?

So that we can have the same 100% coverage reporting regardless of the context of the tests.

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.

[dreamorosi]

As discussed in #3150 the issue seems to have been transient and no longer present, potentially because of a stale branch.

I'll close this for now, and we can reopen if the issue reappears, potentially with steps to reproduce it consistently.

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