Maintenance: remove tests folder from the commons dist package

[am29d]

Summary

Important

Please refer to this comment down below for the latest updates on the scope & tasks for this issue.

In our commons package we export sample resources, which are bundled in our distribution package. We should remove these resources from the distribution package.

Why is this needed?

These sample resources are unnecessary for the production build.

Which area does this relate to?

No response

Solution

No response

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java, and .NET

Future readers

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

[dreamorosi]

Do we treat this as a breaking change?

I agree that they could/should be removed, but we don't know if anyone is depending on them already.

[am29d]

Yes, since the code was available to customers. We use the code only in our tests across most packages. Moving the code to commons/tests would require import additional exports. Alternatively we can create a dedicated testing package to move these kind of utilities and e2e related code.

[dreamorosi]

Alternatively we can create a dedicated testing package to move these kind of utilities and e2e related code.

I think that's the way to go, we should create a new package in the workspace and extract those things not needed at runtime there. Also I don't think we should publish this pkg to npm for now.

---

About the breaking change part, this means we'll have to wait till 2.0

[dreamorosi]

@am29d, do you think we should create a separate issue to create, in due time, a the new unpublished package & move over all the internal references to it while also marking the published one as deprecated?

In this new issue we could:

• Add a new package to the workspaces packages/testUtils, this package will not be published to npm for the time being
• Move all the e2e related utilities, plus the content of the tests (context & events) from commons to testUtils
• Change all the references in our codebase to point to testUtils
• Add a @deprecated annotation to the things we'll want to drop informing that they'll be removed in the next major version

This way we can avoid adding more things inside commons that don't belong there, ease the migration for customers, and also make our life easier when v2 approaches.

Obviously this wouldn't be a priority issue, but I think we could approach it before v2 discussions.

At the same time, this issue here (#1354) would stay open as-is and be closed once we actually remove the files.