We have a TFS 2012 Server and Visual Studio 2015 on the Client side.
The Problem is that when I am building a project containing tests i get the following error on the TFS: F900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid.
On this post i got the information that i have to choose MSTest as the test runner in the build definitions.
But when i try this i get no options to choose for the test runner.
It is greyed out like described in this post. The solution mentioned here is that I had to install a version of Visual Studio 2013 on my build server to get it working.
I already have an installation of Visual Studio 2015 Professional installed on the server but it is still showing the error and i still have no more options to choose from as test runner than Visual Studio Test runner
Why do i not have MSTest as an option as the test runner and how can i fix this?
AND/OR
How can i fix the problem of having this error without installing Visual Studio 2013 on the Build Server?
Related
Vusual Studio 2017 installed. After install Microsoft SQL Server Management Studio 2017 (together with her install Visual Studio 2015 shell (isolated)) and build project, project could not load file or assembly Microsoft.VisualStudio.Diagnostics.PerformanceProvider, Version=14.0.0.0.
After remove Visual Studio 2015 shell (isolated) and rebuild, project work. How can I fix this?
I inherited a project that was created in Visual Studio 2015 with SQL Server Data Tools version 14.
I'm running VS 2017 version 15.6.0 with SQL Server Data Tools 15.1.61801.210
When I try to open the solution it just fails with the below error message. What do I need to do in order to "upgrade" the solution so I can work with it?
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR\LabSOR.dtproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR.sln"
Ended up the SSDT integration elements hadn't installed. Once I did that I could right-click on the project in the solution explorer and reload it, and then it started working.
Our CI environment setup with [TFS Server 2015 + Visual studio build tools 2017]. When I try to run C# based unit test on environment it shows this error
TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid ''.
Then I tried to fix the error by fallowing ways
Installed VS test agent 2015 in the machine https://learn.microsoft.com/en-us/visualstudio/test/lab-management/install-configure-test-agents
Copied C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow from my computer to exact location to CI machine.
Changed test runner from Visual Studio Test Runner to MS Test Runner
But still same error. Looks like tfs server not able to find the test agent folder. Anyone has idea how to fix this
Seems you have VS 2017 Build Tools installed only, no VS IDE on the CI environment.
You need to install VS IDE. VS build tools doesn't contain the "test
platform". In order to run the tests, you require to install full
IDE.
Currently to run the VsTest task, the task has dependency on Visual Studio IDE. But some changes will have in the near future.
We have decided to go with a 'tools installer' which can be used to
get the test platform instead of needing the IDE. If you have the IDE,
great. If you don't, the tools installer will get the test platform on
the agent for you. It is already on backlog and expected to be available on VSTS in a few sprints.
More details please take a look at the discussion in this issue: vstest capability not detected when installed without Visual Studio
Test Logs:
"Queued the TMI run for test run [1594]." TestOutcome 'Warning';
Message 'Warning: Test Run deployment issue: The assembly or module
'Microsoft.VisualStudio.Shell.15.0' directly or indirectly referenced
by deployment item 'C:\Program Files (x86)\Microsoft Visual Studio'
specified by the test settings was not found.'."
Several other similar errors.
Not sure why is it showing so.
It sounds like you need to install the appropriate version of the Agents for Visual Studio package on the machine where you're trying to run these tests.
The 2017 version should be what you're after if you're using Visual Studio 2017.
I Have VS 2015 only installed on my TFS 2013 build server, and get the following error:
TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid ''.
Other sites say to install VS 2013, but why would I have to install VS 2013 on the build server to run unit tests when I have VS 2015 installed?
I have the following switches on my build:
/p:VisualStudioVersion=14.0 /tv:14.0
(This is not a duplicate question as I am using TFS 2013 and am trying to use the Agile Test Runner not MS Test)
Check the solution in this case:
Install VS 2015 or Microsoft Build Tools 2015.
Edit build to use a build process template called TfvcTemplate.12.xaml.
Set MSBuild arguments to /tv:14.0.
But this setting only works for build, not test. As there is no way to set the tool version or tool path for "Run VS Test Runner" activity, installing VS 2013 should be the only way to get rid of this error.
I had a similar problem - was getting the error
TF900547: The directory containing the assemblies for the Visual Studio Test Runner is not valid 'D:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow'.
It ended up being that even though Visual Studio 2015 was installed on the build agent, the user that the Build Agent was running as didn't have read/execute permissions to that folder.