Viktor Hofer
Viktor Hofer
I just observed another misbehavior:  The coverage report is created twice: - vihofer_DESKTOP-803H9R0_2020-04-22_06_59_42\In\DESKTOP-803H9R0\coverage.opencover.xml - 4a408eed-656b-435d-a540-30c285d1c57a\coverage.opencover.xml
You are right :)
FWIW I currently need to clean the TestResults directory manually before VSTest is invoked to make sure that ReportGenerator picks the right coverage results file later. Ideally we would not...
@MarcoRossignoli @nohwnd is someone actively working on this? It's still causing unreasonable pain and the issue is upvoted quite a lot. Also, the milestone seems to be incorrect as 17.1...
> Which version of dotnet-sdk (otr tesplatform is this?) I fixed the file not found exception in rc2 I think. Cool, I'm testing with an RC1 build. > As for...
Not really as the SDK is now in ask-mode afaik. I think it's fine if we do this for 6.0, we might need a 6.0 SDK anyway if we depend...
> but I don't have an idea of a good transport to use. Is memory mapped file low level enough? Why would you need a (network/IO) transport protocol at all?...
> If the network protocol is well defined, I don't mind using that to connect to vstest. It would be nice if there were a reusable library i could reference...
@kartheekp-ms How does that relate to this issue?
I think it would be best if VSTest itself logs all the information that is useful to identify a hanging test and not rely on an adapter's feature for that.