No way to pass build arguments to WebApplicationFactory as is

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

I try to pass build arguments like ["--flag", "2"] to my test host but the only result I can get is --flag=2 or [["--flag=", "--2="]]. The reason is this line.

Describe the solution you’d like

Initially I wanted to push just this:

but then I started to think that -- symbols might make issues too. If you are interested in, I can prepare a better change where you can avoid -- as well.

My current workaround

I just copy/paste DeferredHostBuilder.cs, HostFactoryResolver.cs, WebApplicationFactory.cs and WebApplicationFactoryClientOptions.cs and then do changes inside the project which is awful.

[davidfowl]

@Sergey-Grudskiy can you send a pull request with your change and a unit test for this scenario? I’d love to see what code you wrote.

[kierondye-fraedom]

Is this issue likely to be resolved? I had a similar requirement where I wanted to pass a command line parameter with no value e.g. on the command line it would look like myprocess.exe --param. However, WebApplicationFactory (or DeferredHostBuilder) expects all parameters to be key value pairs separated by = and if there is no value the = gets appended anyway e.g. myprocess.exe --param=. Unfortunately, this prevents me running my integration tests as I planned.