No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I'm looking to learn more about the various ways folks in the Pulumi community are authoring and running tests over their Pulumi IaC.  We have our own guides on testing at <https://www.pulumi.com/docs/using-pulumi/testing/>, but I'd love to hear from anyone applying testing to their IaC in particularly notable or impactful ways, to learn more about the approaches you are using.  Feel free to share here or in DM if you've got any stories you are able to share!

I use TDD with all my projects across all my clients. It's nice to be able to upskill the appdevs when demoing the infra code and commit history to them  :slightly_smiling_face:

Always TS + mocha/jest. The `promise()` method has to be exposed in every file, which is a bit annoying:
```declare module "@pulumi/pulumi" {
  export interface OutputInstance&lt;T&gt; {
    promise(withUnknowns?: boolean): Promise&lt;T&gt;;
  }
}```
It'd be great if there were equivalent of `expect().resolves` and `expect().rejects` (and chai-as-promised's `eventually`) for Outputs :slightly_smiling_face: