TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/TFVC
Similar tohttps://community.smartbear.com/t5/TestComplete-General-Discussions/Failed-to-initialize-the-tfs-api-library/td-p/169418, the solution for whom is insufficient. I've recently started trying to implement TestComplete tests as part of our DevOps Testing release pipeline. I've currently got what is effectively a proof of concept test project in place; it doesn't do anying complex, just pushes some buttons and completes. Everything operates as expected, except each time the release pipeline runs per agent I get a pop-up to the effect that the Microsoft.TeamFoundation.Client assembly cannot be loaded. The entire process halts until this (And sometimes other, effecitvely identical) popup(s) are manually cleared. I understand from the previously linked post that this is due to my utilizing the in-client TFS Source Control integration, but that leaves me at an impasse. If I remove that integration then the errors will disappear, but I'll have to find another, more error prone method of source control for this and future projects. If I leave the integration in, my Automated testing suites will require manual intervention each time which is cumbersome and not scalable. Is there any way to disable Source Control connection on startup, since there really is no need for it to connect just to run some tests? Is there a separate process I could use to run these tests that wouldn't invoke the TestComplete client?Solved1.5KViews0likes5Commentsrunning vstest (Windows 10, TC 12) in isolation
oes running vstest.console.exe /InIsolation require Microsoft Visual Studio be inslalled on the machine it is running? I built a package and tested it on my machine which worked fine. When I copied the TestWindow directory (and all other assorted files) to another VM it did not run. When I did the same thing to a third VM it worked fine. So I am wondering whether Visual Studio must be installed, you cannot just copy the test window to a new machine and run it. So on the two machines where it works, both have this directory: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow On the machine where it does NOT work, there is no directoryC:\Program Files (x86)\Microsoft Visual Studio 11.0\ (nor in Program Files\)Solved2.2KViews0likes3Comments