Hi, thanks for sharing this issue.
I've heard several reports of this issue. I think it happens on systems that are using non-standard VS install locations. After many attempts, I haven't yet been able to reproduce it ... something is going wrong inside the path translation.
It may be worth moving the Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll into your solution and referencing it from there to see if this allows you to work around the problem.
If at all possible, I'd really like to get hold of a server-side log file that shows what's happening when your client connects to the node. If you have time, can you send one through to me? You can submit it through the
contact form.