Faile execute test(s): Error calling Initialization method for test class

Hi.
Today  I want discuss short issue with execute codedUI test on test agent.
If you see this error:

Error calling Initialization method for test class ***: Microsoft.VisualStudio.TestTools.UITest.Extension.UITestException: Automation engine is unable to playback the test because it is not able to interact with the desktop. This could happen if the computer running the test is locked or it’s remote session window is minimized.

Test agent 2013: The setup batch file exited with error code 1

Hi. Today I want show you how resolve errors connect with execute batch file in deploy step before
execute tests.

So in my case I have:

1. TFS 2015
2. Test Controller 2013
3. Test Agent 2013
4. Microsoft Test Manager.

 Imagine, that you have task execute tests before execute tests. You write this script and put it to Microsoft test manager in (Advance -> Scripts).

VNext test agent. Fix issue

As far I started create execute tests UI in VNext build definition.

VNext agent hot connected after add to team foundation server 2015

Hi.
Today is short post about bug of install process of vnext build agent.

VNext build agent : one or many

Hi. Today I want speak about short article: how configure many build agents.
If you have big infrastructure, you should use a lot of build servers. If you used TFS 2013, you probably remember that you can configure number of build agent in UI wizard of team foundation server.

Test Agent :Could not load file or assembly Microsoft.VisualStudio.QualityTools.CodedUITestFramework

Hi all.
Today we are speaking about supporting old system: test agent 2013.

If you have XAML build definition, which build in TFS 2015 test controller and test agent.
But if QC department use Microsoft Test Manager (MTM), you can't use Test Agent 2015.
You should use test agent 2013 with last updates.

Exception Message: Access to the path ...packages\NUnitTestAdapter.2.0.0\lib\nunit.core.dll' is denied

Hi all!

I founded bug in Team Foundation Server 2015.
An today I share the reason.
So the problem connect with build engineers who has TFS 2015 and XAML build definitions.