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

The style of unit tests shown in that article run without ever deploying anything - so output properties like `id` will never be populated - and the callbacks to `apply` will never run. 

This does generally significantly limit the value of this kind of testing - it can be used to verify inputs - but not outputs or behavior. 

There was a follow up article that shows a technique that can allow running unit tests during updates - which can allow verifying things like this: <https://www.pulumi.com/blog/unit-testing-infrastructure-in-nodejs-and-mocha/>

But frankly in my experience by far the highest value testing you can have is tests that spin up real infrastructure and validate it before tearing down. These can still be “unit tests” in the sense that they test one component at a time - but they can test the actual correctness of your infrastructure. 

There’s a great project - Pitfall - for doing this kind of testing with Pulumi in Python - see <https://pulumi-community.slack.com/archives/CB36DSVSA/p1573146387034300>. 

<@UQG960ZUG> Let me know if you have any questions