Hello!
- Vote on this issue by adding a 馃憤 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
There are currently overload test functions defined that allow you to test the outputs of a mock pulumi stack during unit testing, however there is no support for this of stack output testing when using a service provider.
The TestWithServiceProviderAsync doesn't offer any overloads that expose the outputs from a stack. Link here.
But there are examples of the TestAsync function that do exactly this. Link here.
Ideally the TestWithServiceProviderAsync function would have an expanded overload to support a return type with Task<(ImmutableArray<Resource> Resources, IDictionary<string, object?> Outputs)
Affected area/feature
dotnet SDK testing
Hello!
Issue details
There are currently overload test functions defined that allow you to test the outputs of a mock pulumi stack during unit testing, however there is no support for this of stack output testing when using a service provider.
The
TestWithServiceProviderAsyncdoesn't offer any overloads that expose the outputs from a stack. Link here.But there are examples of the
TestAsyncfunction that do exactly this. Link here.Ideally the
TestWithServiceProviderAsyncfunction would have an expanded overload to support a return type withTask<(ImmutableArray<Resource> Resources, IDictionary<string, object?> Outputs)Affected area/feature
dotnet SDK testing