dotnet-dotcover ... dotnet run in a blazor wasm project does not cover clientside code

[PlatypusK]

command run
dotnet-coverage collect -o "D:\output-dotnet-coverage.xml" --output-format xml dotnet run

Building...
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:7052/
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5052/
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: D:\Workspace\Clone\InterestCalculator\InterestCalculator.Client
info: Microsoft.Hosting.Lifetime[0]
Application is shutting down...
Canceling...
Code coverage results: D:\output-dotnet-coverage.xml.

this will produce a coverage file of the serverside code, but no mention of clientside code even though both are running

Note that it seems like the client has issues connecting to the server as well when run in this fashion. The app runs fine if run with just dotnet run.

The idea here is to start a clientside app locally, then run e2e tests with coverage using playwright or similar frameworks. Is this a supported option?

[PlatypusK]

Expected Behavior
Collecting coverage on a locally hosted clientside wasm blazor app when using dotnet run with the dotnet-coverage tool

Steps To Reproduce
Create dotnet wasm hosted project
run "dotnet-coverage collect -o "D:\output-dotnet-coverage.xml" --output-format xml dotnet run"
Do anything in the clientside on the browser
Check in the generated coverage xml file if it contains clientside coverage

Exceptions (if any)
No response

.NET Version
6.0.111

Anything else?
I realize it may take debug mode or similar to do this, so would love for some instructions on how to enable this. Looked extensively on the web for a way to get coverage for e2e clientside blazor, and found nothing so far. I would very much prefer a cli solution so that it can be done in a ci pipeline

[ghost]

Tagging subscribers to this area: @dotnet/area-extensions-hosting
See info in area-owners.md if you want to be subscribed.

Issue Details

---

command run
dotnet-coverage collect -o "D:\output-dotnet-coverage.xml" --output-format xml dotnet run

Building...
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:7052/
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5052/
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: D:\Workspace\Clone\InterestCalculator\InterestCalculator.Client
info: Microsoft.Hosting.Lifetime[0]
Application is shutting down...
Canceling...
Code coverage results: D:\output-dotnet-coverage.xml.

this will produce a coverage file of the serverside code, but no mention of clientside code even though both are running

Note that it seems like the client has issues connecting to the server as well when run in this fashion. The app runs fine if run with just dotnet run.

The idea here is to start a clientside app locally, then run e2e tests with coverage using playwright or similar frameworks. Is this a supported option?

Author:	PlatypusK
Assignees:	-
Labels:	area-Extensions-Hosting
Milestone:	-

[radical]

cc @TanayParikh

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

command run
dotnet-coverage collect -o "D:\output-dotnet-coverage.xml" --output-format xml dotnet run

Building...
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:7052/
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5052/
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: D:\Workspace\Clone\InterestCalculator\InterestCalculator.Client
info: Microsoft.Hosting.Lifetime[0]
Application is shutting down...
Canceling...
Code coverage results: D:\output-dotnet-coverage.xml.

this will produce a coverage file of the serverside code, but no mention of clientside code even though both are running

Note that it seems like the client has issues connecting to the server as well when run in this fashion. The app runs fine if run with just dotnet run.

The idea here is to start a clientside app locally, then run e2e tests with coverage using playwright or similar frameworks. Is this a supported option?

Author:	PlatypusK
Assignees:	-
Labels:	arch-wasm, untriaged, area-Extensions-Hosting
Milestone:	-

[lewing]

This is an interesting case to consider @radical @maraf

[rodolfograve]

+1 ... We are also interested in this use case.