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

Unit tests are usually not performed on Pulumi projects: Pulumi ComponentResources are a more appropriate level to unit test at.
ComponentResources shouldn't be using pulumi.config, they should be constructed with configurable paramaters passed in to their constructors.
Is it feasible to re-design your resources and projects to allow you to inject values into resources, instead of injecting test data into your context `config`?

If you're using property or integration testing, then you're really running Pulumi, and you shouldn't need to inject anything into your test context `config`. Just have a config for your test project or stack.