Problem Statement
I'm trying to get access to the to the configureBuilder param in DistributedApplicationTestingBuilder.CreateAsync used here
It seems like maybe it could be handled the same way as AppFixture.Args?
If you're willing to take a PR let me know, I should have some time this weekend.
Thanks for all the effort you've put into TUnit, it's working out fantastically for our use-case.
Proposed Solution
Add a protected virtual to AppFixture similar to protected virtual string[] Args => []; something like:
protected virtual Action<DistributedApplicationOptions,HostApplicationBuilderSettings> ConfigureCallback => static (_, _) => return; and pass it to DistributedApplicationTestingBuilder.CreateAsync
Alternatives Considered
I did some poking around but I didn't see another way of getting access other than through the CreateAsync function. You could copy/paste the whole InitializeAsync but that could cause hard to find issues if the internal implementation changes since it wouldn't be called anymore.
Feature Category
Other
How important is this feature to you?
Important - significantly impacts my workflow
Additional Context
No response
Contribution
Problem Statement
I'm trying to get access to the to the
configureBuilderparam in DistributedApplicationTestingBuilder.CreateAsync used hereIt seems like maybe it could be handled the same way as
AppFixture.Args?If you're willing to take a PR let me know, I should have some time this weekend.
Thanks for all the effort you've put into TUnit, it's working out fantastically for our use-case.
Proposed Solution
Add a protected virtual to AppFixture similar to
protected virtual string[] Args => [];something like:protected virtual Action<DistributedApplicationOptions,HostApplicationBuilderSettings> ConfigureCallback => static (_, _) => return;and pass it toDistributedApplicationTestingBuilder.CreateAsyncAlternatives Considered
I did some poking around but I didn't see another way of getting access other than through the
CreateAsyncfunction. You could copy/paste the wholeInitializeAsyncbut that could cause hard to find issues if the internal implementation changes since it wouldn't be called anymore.Feature Category
Other
How important is this feature to you?
Important - significantly impacts my workflow
Additional Context
No response
Contribution