Example: how to unit test a component resource #1063
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An example that would have really helped me in the past – when I started breaking things up into Component Resources, I really missed any notes on how to test. It's possible to figure it out but some "best practice" would be great
https://www.pulumi.com/docs/intro/concepts/resources/#components
Especially in the tutorial on Component Resources, there is no mention on unit testing them in isolation
https://www.pulumi.com/docs/tutorials/aws/s3-folder-component/
I may have done too much here – sub-foldered into
mocha/
, changed how mocha is called (to use the node_modules, rather than a global install)