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

This isn't a problem with _setMocks_, just with the runtime not detecting that you're running as a test. Normally it does detect this correctly, but it is possible to "break" this detection. For example, in some of my test code I use _pulumi.runtime.registerStackTransformation()_ which does not play well with Pulumi's test-detection logic.

The workaround is to run the tests where this problem happens within a _pulumi.runtime.runInPulumiStack()_ block. You don't need to change your _pulumi.runtime.setMocks()_ code, just the tests where Pulumi resources are constructed.

In my code, the calls to _setMocks()_ and _runInPulumiStack()_ are at the same level. It's important not to nest _setMocks()_ inside _runInPulumiStack()_.