Docs: Add section on how to contribute tests to the overall project

[sthulb]

What were you searching in the docs?

I was trying to find a section on how to setup a local test harness so I could write some tests

Is this related to an existing documentation section?

No response

How can we improve?

There needs to be a contributing/testing section in the docs to help people get up to speed faster with writing tests for the project.

Got a suggestion in mind?

No response

Acknowledgment

• I understand the final update might be different from my proposed suggestion, or refused.

[leandrodamascena]

Hi @sthulb! Are you talking about testing in general with Powertools? In our contributing guide we have a GitPod template ready to run the Powertools tests (local + e2e) and I wonder if that's not enough.

https://github.com/aws-powertools/powertools-lambda-python/blob/develop/CONTRIBUTING.md#contributing-via-pull-requests

Thank you.

[sthulb]

@leandrodamascena I was thinking more like adding a section like: https://developer.hashicorp.com/terraform/plugin/testing/testing-patterns

[rubenfonseca]

While there may not be a dedicated "testing" section in the documentation, it's worth noting that each utility within the aws-powertools library typically includes a "Testing Your Code" section. (Example: batch processing). This section provides guidance on how to write tests specifically for that utility.

Expanding this with a dedicated section for testing will exponentially increase the effort to maintain the code. For now I will close the issue, and I ask you to reopen if necessary.

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

[leandrodamascena]

@heitorlessa is working on this documentation.

Reopening.

[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 2.26.0 version!