You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
I've raised a PR #101 with the change I think needs to happen to facilitate this but I may need some review support as I don't know if this constitutes a change requiring change log updates.
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
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 withTask<(ImmutableArray<Resource> Resources, IDictionary<string, object?> Outputs)
Affected area/feature
dotnet SDK testing
The text was updated successfully, but these errors were encountered: