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
When we executed a test execution using dotnet test someProj.csproj the test execution takes 19 seconds. After we add packages with dotnet add package AltCover it takes more than 1 hour.
Is this normal?
Is there a way to minimise this?
The text was updated successfully, but these errors were encountered:
No, that is not normal. While there is necessarily some overhead in the coverage gathering, including needing to serialize the output in multi-threaded situations, I've not observed that factor of slowdown myself.
For example, AltCover's own unit tests take 50s by themselves, but that only increases to 2 minutes when self-instrumenting, and that's including build time.
Can you isolate a simple example of the problem that you can share?
I have made changes in 5.0.665 which have improved the throughput and speeded unit tests for me; however I've not had such a pathological case to work with, si I don't know if it will make any difference for your case.
Release v5.3.675 makes some significant speed-ups for dotnet test cases which have heretofore been limited by the data collection mechanism used to work around vstest.console's hard guillotine at process exit.
When we executed a test execution using
dotnet test someProj.csproj
the test execution takes 19 seconds. After we add packages withdotnet add package AltCover
it takes more than 1 hour.The text was updated successfully, but these errors were encountered: