We're having trouble with code coverage on our Visual Studio Online (VSTS) build definition, where no results are returned when we define a custom .runsettings file. Locally this is working fine, ...

Reading through https://msdn.microsoft.com/en-us/library/jj635153.aspx I have created a .RunSettings files with a few parameters similar to the example: <TestRunParameters> <Parameter n...

I have a set of unit tests in a .NET Core project and using a runsettings file. I am trying to setup Azure DevOps to do automated testing on my deployments. As part of this process, I need to overr...

I am seeking a way to define assembly resolution values using relative file paths. I am approaching this by defining and referencing an environment variable as recommend by the Microsoft documentat...

I'm writing xUnit unit test cases for a dotnet core application which uses DocumentDB (CosmosDB) as storage. The unit test are written to execute against the local cosmos db emulator. On the Azure ...

I am trying to generate code coverage report using vstest.console.exe. I am also using .runsettings file and passing it as a parameter. Whatever I am trying to do, it generates a coverage report f...

I have a UnitTests.dll, to which Common.dll is referenced (both built with VS2015). I have following directory structure: C:\Test\ - UnitTests.dll - UnitTests.runsettings C:\Bin\ - Common.dll...

I'm trying to exclude all namespaces but Acme.Foundations.Web.Ext.Controllers from assembly Acme.Foundations.web.ext.dll. Please help create a runsettings file. <DataCollectionRunSettings> ...

I'm trying to make Visual Studio's Code Coverage tool useful. I'm working on a legacy project and in order to refactor all this code I add unit tests. The problem is, when I measure code coverage I...

I'm trying to restrict the assemblies that get analyzed in the Code Coverage procedure in TFS by using a runsettings file, but some assemblies insist in being analyzed even if I exclude them explic...

we have moved from VS2010 to VS2013 environment. Our solution has over 5K unit tests and on VS2010 they took about 5 minutes while on VS2013 they are taking about 20 minutes. We saw that there is ...