Maintenance: streamline tracer e2e tests

[dreamorosi]

Summary

As discussed during the review of #3012 (here), the end to end tests for the Tracer utility have become unwieldy and have a lot of overlap. This has been the result of years of adding test cases to cover new features.

We should streamline the test structure so that the overlap & duplication is reduced.

Why is this needed?

So that the tests are more maintainable and also so that we can reduce the number of traces emitted for each test, which in case of multiple subsequent test runs lead to excessive noise.

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.

[github-actions]

This is now released under v2.8.0 version!