Test discovery fails with collect code coverage enabled if global thread_local smart pointer is in the test code about googletestadapter HOT 2 CLOSED

Thanks for the great bug report! However, I don't think that GTA is to blame here since it merely runs your executable with .NET's Process framework, but is not involved at all with collecting code coverage information - this is done by vstest.console.exe. I fear that I can't help here.

I would maybe try a different gtest version then the one provided by MS (e.g. add the gtest code to your solution, build it yourself, and link that version), or to talk to the MS Test guys providing vstest.console.exe. One more thing you could try is to use Test Adapter for Google Test (MS' clone of GTA) instead of GTA, but I expect the same behavior from that one.

Let me know if you could solve the problem - might be something for the trouble shooting section of the GTA docs!

from googletestadapter.

I will close this issue since it probably indeed is a VsTest problem, but in case relevant information is added to microsoft/codecoverage#32 maybe you could leave a short notice here - thanks!

from googletestadapter.